prompt stringlengths 1 63.6k | completion stringlengths 1 53.1k |
|---|---|
Hello, When trying to install local .deb package, on Debian 10, I get the following errors. dpkg: warning: 'ldconfig' not found in PATH or not executable dpkg: warning: 'start-stop-daemon' not found in PATH or not executable dpkg: error: 2 expected programs not found in PATH or not executable The package can't be installed. | questlinq wrote:Do I always need to use "su -" in Buster? As explained by Soul Singin' and roseway, if you need to run anything which is not in your user PATH, yes. I sometimes run apt install (which is in /usr/bin/ therefore in user's PATH) without the dash after su, , to install a locally downloaded package. apt install is better than dpkg -i as it will also resolve and download dependencies if there are any. eg. - Code: Select allapt install ./<downloaded-package> Don't forget the ./ (or give the full path) so apt knows it's installing locally and not from repository. Of course you'd still need su - if the installer calls ldconfig or anything else in /usr/sbin/ . See also - http://forums.debian.net/viewtopic.php?f=16&t=142973 |
Hi all, I have an issue with my italian keyboard and Debian 10. When laptop starts characters do not match with my laptop keyboard. The file "/etc/default/keyboard" seems correct, in my opinion: Code: Select all# KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="it" XKBVARIANT="" XKBOPTIONS="" BACKSPACE="guess" I have found a rapid fix, but it is not final, just typing on terminal, after every logon Code: Select allsetxkbmap it but it is a temponary solution. After reboot, the layout keyboard is not correct again. During OS installation I have choosen italiay keyboard layout and english language. Before today all worked fine! Someone have any ideas to fix this problem? Thanks in advance | I would try Code: Select all# dpkg-reconfigure locales |
I have a multiboot system with Buster and another distro whose GRUB2 is the master for the system. The other distro allows the installation of several kernels that I can choose at the GRUB menu, but I've tried installing the most recent RT version available in Buster, updating GRUB, and it doesn't show the RT as an option. just the vanilla 4.19 and its debug. Is there a way I can set up Buster to allow me to choose the vanilla or RT at boot, and what tricks if any are needed to get this to show up in GRUB? | You will need to update grub from the OS controlling it, reboot and it should show the new kernels. |
Debian Buster (KDE) I have a fresh install of Debian. I want to use KDE Partition Manager but after entering my root password Kdesu just hangs there frozen for eternity, until I kill the process. Same happens to Discovery and Muon Package Manager when trying to configure the Sources List. Opening Bleachbit in Root or when Muon asks Root Password to install programs don't have this issue tho. Weird, I've never experienced this behavior on Kubuntu, Manjaro, and/or OpenSuse. I tried using the Su command but then I get this error: "No support tools were found for file systems currently presen on hard disks in this computer" * But I already have e2fsprogs and ntfs-3g installed What should I do? Honestly, I don't even know why people say Debian is "extremely stable". Aside from this issue, I have encountered other minor issues that have been reported by other people, years have passed by and no fixes have been made. Like for example Konsole crashes when trying to download/install a colorsheme via it's add-on or when Falkon crashes all the time and it even freezes the entire desktop.. | Don't use it. I've quoted this very good explanation from https://askubuntu.com/questions/1044354 ... ot-working This is a very much more complex question than it first appeared to me to be First of all, it is highly recommended not to use kdesu or kdesudo to run graphical applications as root or with administrative privelages. Why is it not recommended? The short answer is that it is considered a substantial security risk. The security risk is being discussed at length (and disputed) in a number of different posts and bug reports. @DK Bose kindly provided some links as a good starting point for anyone who wants a bit more detail: https://www.kubuntuforums.net/showthrea ... er-problem The above link led me to some other links which show a 'lively' discussion about it: https://bugs.kde.org/show_bug.cgi?id=152150 and also https://bugs.kde.org/show_bug.cgi?id=179678 which in turn led me to a blog post about the security problem that is being discussed: https://blog.martin-graesslin.com/blog/ ... s-as-root/ Basically, to prevent users from exposing themselves to this security risk, running Kate or Dolphin as root has been disabled. Kate now allows you to save system files etc. by asking you to enter your password when you require permission to save your file (via Polkit - i.e a system dialogue box appears requesting permission). This should mean it is not necessary to run Kate as root. Dolphin will be doing the same in the near future but the change has not been implemented yet. (On the sometimes heated discussions about this change, there were criticisms that disabling running Dolphin as root should not have been implemented until an alternative was in place. The counter argument was that the security risk was too great to allow it.) In the meantime, there are other file managers such as PCManFM or Thunar which allow running as root (for those who understand the security implications but require the functionality). I can't think of a lot of situations where it would be necessary to run a graphical user application as root outwith the 'editing system files' scenario. Kate can do this now without needing to be run as root. Some of the use cases that sparked arguments against disabling running Dolphin as root, involved users wanting to create symlinks on their system files whilst using the GUI and also for penetration testing where, for example, Kali Linux runs the entire session as root. The other reccurring argument was that if a user was aware of the security risk and wanted to run graphical applications as root anyway, then they should be allowed to do so. kdesudo is not installed in Kubuntu 18.04 by default and is no longer in the Debian and Ubuntu repositories. It is not recommended to be used because it is unmaintained (and the general suggestion that you shouldn't be running graphical user interface programs with X as root). kdesu is installed (as part of kde-cli-tools) but is not in your $PATH by default. You can access the binary from /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu (and create a symlink in your /usr/local/bin directory if you don't fancy typing that out each time you want to use it - https://www.kubuntuforums.net/showthrea ... ht=kdesudo), but it is not recommended that you do so (due to the security implications) and will not work for Kate and Dolphin anyway. GParted works very well in KDE and comes with the appropriate files to allow execution under pkexec. Synaptic is far superior to Muon and Discover. |
hello all, i've the following distro: Linux nas 4.19.0-0.bpo.5-amd64 #1 SMP Debian 4.19.37-4~bpo9+1 (2019-06-19) x86_64 GNU/Linux after a long time i've finally found a working driver (at least compiling and installing) https://github.com/minjae/rtl8821au.git i can see the usb device: root@nas:~/rtl8821au# lsusb Bus 001 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub but i can only see the ethernet interface root@nas:~# lshw -C network *-network description: Ethernet interface product: VT6102/VT6103 [Rhine-II] vendor: VIA Technologies, Inc. physical id: 12 bus info: pci@0000:00:12.0 logical name: enp0s18 version: 7c serial: 00:19:66:99:b9:14 size: 100Mbit/s capacity: 100Mbit/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.5.1 duplex=full ip=192.168.1.200 latency=32 link=yes maxlatency=8 mingnt=3 multicast=yes port=MII speed=100Mbit/s resources: irq:23 ioport:c000(size=256) memory:fdfff800-fdfff8ff any ideas? thanks a lot Emilio | emiliocb4 wrote:after a long time i've finally found a working driver (at least compiling and installing) https://github.com/minjae/rtl8821au.git I think that is the wrong driver for your device. Try this one - https://github.com/jeremyb31/rtl8822bu And you may also need to install the package firmware-realtek from non-free repo. Found on https://forum.peppermintos.com/index.php?topic=6813.0 using search term debian 0bda:b812 |
Code: Select all# # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=ca5368ef-585d-447b-adfd-84fadb704cc7 / ext4 errors=remount-ro 0 1 #UUID="1d101b5b-ac69-4afa-a86d-6f538edd9461" /home TYPE="ext4" defaults 0 2 swap was on /dev/sda2 during installation UUID=ba9e2734-9179-4352-84be-30469ee07b3c none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 LABEL="Data" UUID="3477a04f-d073-46d9-8c7e-237012714900" /media/ckosloff/Data ext4 defaults 0 0 I had to reinstall system from netinst CD and missed to set mount point for home at that time, so I thought it would be easy to set it later by editing fstab, please note that that line is commented out, since system would not boot normally because failing to mount home, however the UUIS is pasted from output of blkid. Another problem happens with last line, UUID pasted with same method, yet Data does not load form its mount point, I have to enter root password to mount it. Please help, I don't want to go through reinstalling system all over again. Thanks in advance. | Remove the quotes on both those lines |
Hello, I have a Debian 10 installation done as a server - no Desktop or WM. The setup works, but I'm having issues with firewall. I can add IPTABLES rules, although "iptables -L" command fails with iptables: command not found I can see from Debian documentaion that iptables is being replaced by nftables. Could this be the issue to command not found problem? | Check $PATH. |
what have i done wrong here Code: Select all# cat /etc/default/locale # File generated by update-locale LANG="en_ZA.UTF-8" LANGUAGE="en_ZA.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_GB.UTF-8" aptitude returns Code: Select allperl: warning: Please check that your locale settings: LANGUAGE = "en_ZA.UTF-8", LC_ALL = (unset), LC_TIME = "en_GB.UTF-8", LC_NUMERIC = "en_US.UTF-8", LANG = "en_ZA.UTF-8" are supported and installed on your system. perl: warning: Falling back to a fallback locale ("en_ZA.UTF-8"). | Try Code: Select all# locale-gen |
Hi to all, I have a problem with networking service on Debian 10(Buster), VPS server. I tried to search but to no avail. The problem: networking.service fails to start!? Network, ssh connection, iptables, psad, etc are working as configured.The ufw service shows a problem with "chain ufw-not-local", but ufw status verbose && restating the service works. I have disabled ipv6 via /etc/sysctl.conf and grub, though, but does not seem as a problem. Commands are showing proper name 'eth0' $/etc/networking/interfaces $ ls /sys/class/net/ $ ifconfig -a $ ip a $ fquery eth0 root@hostname:~# ifup eth0 RTNETLINK answers: File exists ifup: failed to bring up eth0 #systemd log $journalctl -xe -- Subject: A start job for unit networking.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit networking.service has begun execution. -- -- The job identifier is 213. Sep 07 15:47:38 xxxx(hostname) ifup[21005]: RTNETLINK answers: File exists Sep 07 15:47:38 xxxx(hostname) ifup[21005]: ifup: failed to bring up eth0 Sep 07 15:47:38 xxxx(hostname) systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit networking.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Sep 07 15:47:38 xxxx(hostname) systemd[1]: networking.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit networking.service has entered the 'failed' state with result 'exit-code'. Sep 07 15:47:38 xxxx(hostname) systemd[1]: Failed to start Raise network interfaces. -- Subject: A start job for unit networking.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit networking.service has finished with a failure. Any way I can solve or debug this problem? Regards, Tomislav | just misconfigured /etc/hosts for particular VPS provider disregard >> In Stretch disabling ipv6 worked by: $ vim /etc/sysctl.conf Add the following at the bottom of the file: $ net.ipv6.conf.all.disable_ipv6 = 1 $ net.ipv6.conf.default.disable_ipv6 = 1 $ net.ipv6.conf.lo.disable_ipv6 = 1 $ sysctl -p && GRUB line in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" $ update-grub In Buster, at least for now, there is an additional step, $ vim /etc/network/interfaces comment out #iface eth0 inet6 static #address xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx #netmask 64 #gateway xxxx::x #accept_ra 0 #autoconf 0 #privext 0 The networking service is loaded at the boot && everything works. Regards, Tomislav |
I have a fairly plain system, new install of Buster via non-free iso late May to June - jigdo to update it 3 times for dry runs. KDE Dull repos Code: Select allinxi -r Repos: Active apt repos in: /etc/apt/sources.list 1: deb http://debian.mirror.rafal.ca/debian/ buster main non-free contrib 2: deb-src http://debian.mirror.rafal.ca/debian/ buster main non-free contrib 3: deb http://security.debian.org/debian-security buster/updates main contrib non-free 4: deb-src http://security.debian.org/debian-security buster/updates main contrib non-free 5: deb http://download.virtualbox.org/virtualbox/debian bionic contrib Active apt repos in: /etc/apt/sources.list.d/spideroakone.list 1: deb https://apt.spideroak.com/ubuntu/ release restricted paxmark@dbnbuster:/$ ^C standard kernel Code: Select all inxi CPU: Dual Core Intel Core i3-4170 (-MT MCP-) speed/min/max: 880/800/3700 MHz Kernel: 4.19.0-5-amd64 x86_64 Up: 1h 23m Mem: 2283.3/11469.6 MiB (19.9%) Storage: 2.27 TiB (20.4% used) Procs: 204 Shell: bash 5.0.3 inxi: 3.0.32 I was having some wierd hiccups, lets wait and see, except for the s l o w startup of printing on HP laser cups. Various places (including Siduction) mentioned apparmor and problems. apt remove apparmor and my printng was back to normal and a faster response in some things apparmor just re-appeared in the update Code: Select all aptitude why apparmor i linux-image-amd64 Depends linux-image-4.19.0-5-amd64 i A linux-image-4.19.0-5-amd64 Recommends apparmor I just let it by, will check printing later. But I would be appreciative of good info on pros and cons or apparmor. EDIT Later: I marked as as solved. | In a totally unrelated exercise I had virt-manager fail to connect to the default URI, and it blamed apparmor. Long story, but I could cli my way into a working vm. In a quick review I saw libvirt-daemon-system was somehow orphaned and removed during a partial upgrade. Put that back in and the apparmor error went away. Point is, apparmor errors may not be apparmors' fault. |
hello again, I'm trying to set up iptables instead of ufw on Debian 10, i basically need to forward 5 external ports to a kvm/qemu instance (22, 80, 443, 8448, 3478), host occupies 192.168.1.170 on the local network, guest connects via virbr0 (virtio) adapter, it's IP is 192.168.122.182 (with gateway 192.168.122.1). Here is the default firewall setup for the host: Code: Select all*filter # Allows all loopback (lo0) traffic and drop all traffic to 127/8 that doesn't use lo0 -A INPUT -i lo -j ACCEPT -A INPUT ! -i lo -d 127.0.0.0/8 -j REJECT # Accepts all established inbound connections -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # Allows all outbound traffic # You could modify this to only allow certain traffic -A OUTPUT -j ACCEPT # Allows HTTP and HTTPS connections from anywhere (the normal ports for websites) -A INPUT -p tcp --dport 80 -j ACCEPT -A INPUT -p tcp --dport 443 -j ACCEPT # Allows Federation port for Synapse. -A INPUT -p tcp --dport 8448 -j ACCEPT # Allows coturn service. -A INPUT -p tcp --dport 3478 -j ACCEPT # Allows SSH connections # The --dport number is the same as in /etc/ssh/sshd_config -A INPUT -p tcp -m state --state NEW --dport 22 -j ACCEPT # Now you should read up on iptables rules and consider whether ssh access # for everyone is really desired. Most likely you will only allow access from certain IPs. # Allow ping # note that blocking other types of icmp packets is considered a bad idea by some # remove -m icmp --icmp-type 8 from this line to allow all kinds of icmp: # https://security.stackexchange.com/questions/22711 -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT # log iptables denied calls (access via 'dmesg' command) -A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7 # enable logging generally #-A INPUT -j LOG # Reject all other inbound - default deny unless explicitly allowed policy: -A INPUT -j REJECT -A FORWARD -j REJECT COMMIT Does this look okay? I essentially want to allow outgoing and deny incoming packets, except for the 5 ports i wish to forward (22, 80, 443, 8448, 3478). Here is the guide for just forwarding port 22 to a kvm instance just using 'hooks' on the hostOS: https://wiki.libvirt.org/page/Networkin ... onnections I've modified it like so, i'm also curious if this looks alright: Code: Select all#!/bin/bash # IMPORTANT: Change the "VM NAME" string to match your actual VM Name. # In order to create rules to other VMs, just duplicate the below block and configure # it accordingly. if [ "${1}" = "kvm1-website.org" ]; then # Update the following variables to fit your setup GUEST_IP=192.168.122.182 GUEST_PORT1=22 HOST_PORT1=22 GUEST_PORT2=80 HOST_PORT2=80 GUEST_PORT3=443 HOST_PORT3=443 GUEST_PORT4=8448 HOST_PORT4=8448 GUEST_PORT5=3478 HOST_PORT5=3478 if [ "${2}" = "stopped" ] || [ "${2}" = "reconnect" ]; then /sbin/iptables -D FORWARD -o virbr0 -d $GUEST_IP -j ACCEPT /sbin/iptables -t nat -D PREROUTING -p tcp --dport $HOST_PORT1 -j DNAT --to $GUEST_IP:$GUEST_PORT1 /sbin/iptables -t nat -D PREROUTING -p tcp --dport $HOST_PORT2 -j DNAT --to $GUEST_IP:$GUEST_PORT2 /sbin/iptables -t nat -D PREROUTING -p tcp --dport $HOST_PORT3 -j DNAT --to $GUEST_IP:$GUEST_PORT3 /sbin/iptables -t nat -D PREROUTING -p tcp --dport $HOST_PORT4 -j DNAT --to $GUEST_IP:$GUEST_PORT4 /sbin/iptables -t nat -D PREROUTING -p tcp --dport $HOST_PORT5 -j DNAT --to $GUEST_IP:$GUEST_PORT5 fi if [ "${2}" = "start" ] || [ "${2}" = "reconnect" ]; then /sbin/iptables -I FORWARD -o virbr0 -d $GUEST_IP -j ACCEPT /sbin/iptables -t nat -I PREROUTING -p tcp --dport $HOST_PORT1 -j DNAT --to $GUEST_IP:$GUEST_PORT1 /sbin/iptables -t nat -I PREROUTING -p tcp --dport $HOST_PORT2 -j DNAT --to $GUEST_IP:$GUEST_PORT2 /sbin/iptables -t nat -I PREROUTING -p tcp --dport $HOST_PORT3 -j DNAT --to $GUEST_IP:$GUEST_PORT3 /sbin/iptables -t nat -I PREROUTING -p tcp --dport $HOST_PORT4 -j DNAT --to $GUEST_IP:$GUEST_PORT4 /sbin/iptables -t nat -I PREROUTING -p tcp --dport $HOST_PORT5 -j DNAT --to $GUEST_IP:$GUEST_PORT5 fi fi Any inputs appreciated, thank you. Edit: macvtap with passthrough > virtio and a VLAN, at least for this humble application (home server) | I'm blurry on your purpose. Personally, I ditched virbr and use macvtap only for shared physical ports. By default, all guest see each other, host is invisible. The way it should be. To involve the host in the network, physically loop an additional host port to an external hub/switch. To give a single VM access to/from the host, vfio pass an additional port to the external hub/switch. Such hardware solution will stay working, software workarounds will continually need fixed. Further, it would be best to have separate routes for internet and intranet. You also could look into using the spice channel instead of the eth interface. |
I came up with a strange issue. Using VMM 2.0.0 from Buster the "Add a Storage Volume" dialog no longer includes a 'backing store' option. It is usually below the "Format' drop down , and above the 'Storage Volume Quota' statement. Helpful would simply be someones's confirmation a default VMM install in Buster does have this option? Unhelpful would be trying to digest the status or health of this system. 1. Rolling update from Jessie to Stretch to Buster. Synaptic makes no complaints, nothing broken, etc. 2. Has been many things, broken and fixed many times. Issue goes back before Busters move to stable. 3. Disposable copy. Note on #2, most recently I did try to get nftables working and removed iptables. Broke, and put it back. Continued working on the new machine versions, etc, everything working, past vm's, layers storage vm's (so it does understand backing stores) and then went to create a new test layer, and the option is missing. First time I noticed, I checked an older image from before the above testing, same thing. Is it remotely possible they removed it? Yes I can try an earlier image, start over, just thought someone else has noticed. It's odd it's simply not there, I'd expect it to be grayed out if I had a dependency issue. In comparable package list, I see nothing missing. | Well, without any confirmation I'll just start guessing... The function really is gone. I found a screenshot, also with the option missing. My heart sank. I created these system a few years ago for the express purpose of preserving obsolete stuff that has no replacement. It never occurred to me that the hypervisor itself could become frozen in time. So my Stretch has been given an indefinite lease on life, it won't be upgraded. There is a reason the stretch version has no browser, no mail, no nothing. I wonder if a skip to bullseye will be possible in few years. The buster version is not an improvement so far. I continued with other stuff, have some more testing to do, but what's the use, I want a divorce. So I consulted the counselor, his name is root, at least my ROOT environment still works. Ya know, where I can do things without typing su sudo sudio password ever 10 seconds...I did some digging and found the issue. Buster has proven to have a few things in flux, like every release does - things that old ways are leaving, new ways are not solidified, so things don't work without actually being broken. Root stuff (pkexec/gksu/Phil Collins), iptables is still required, and more. Add another. Qemu-img, a favorite of mine, has changed. It appears to be improved. Syntax changed slightly. I was close to using dynamite since old syntax was not working but I did manage to create a new layer qcow on a 'backing store'. So technically, buster still works and I simply need the cli to do it. BACKWARDS we go. Then my guess solidified. VMM 2.0.0 maybe does not have the new way baked in. So no more easy GUI'ing. Other qcow capabilities did make it into the new VMM 2.0 gui, looks like sparseness improved - something that needed cli help in the past, so maybe we're even. I still love debian, I'll stay. I do wish gui cpu pinning was still there, that was absent from stretch - the last time I blew a fuse. |
Hello, I'm trying to mount a NTFS drive so that it has execute permission. My /etc/fstab has the line, Code: Select all/dev/sda1 /home/user/ntdrive ntfs-3g rw,exec,user,auto,uid=1000,gid=1000,umask=0022 0 0 and when booting the drive mounts itself fine. However, Code: Select all$ mount | grep ntdrive /dev/sda1 on /home/user/ntdrive type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,user) What gives here? I specifically asked for exec but got noexec. Any advice? Thanks, Richard | Put exec after user |
Dual boot laptop (32): sda1: debian 10 with RT kernel sda3: debian 10 After upgrading sda3 from debian 9 to 10 sda3 is the default os in grub. sda3 is the first option in the grub menu I performed "sudo update-grub" in sda1 to change the default os to sda1 but that did not work. Then I did a new "sudo grub-install /dev/sda" in sda1. Now the first option is the sda1 os but the highlighted os is still sda3. In the file /etc/default/grub I only changed the time, nothing else: GRUB_DEFAULT=0 GRUB_TIMEOUT=2 How can I make the os on sda1 the default option????? | To change the default in GRUB edit the GRUB_DEFAULT option in /etc/default/grub from whichever operating system the grub-install command was last run and use the update-grub command to update the configuration file. https://www.gnu.org/software/grub/manua ... figuration Why do you have two separate Debian systems? It is possible to have two different kernels installed in the same system and use GRUB to choose between them. |
The solution I used on my Technoethical T400s for Stretch (on GNOME 3) unfortunately doesn't seem to work on my Acer Extensa 5220 with Buster (using XFCE). Code: Select all$ egrep -i 'synap|alps|etps|elan' /proc/bus/input/devices N: Name="SynPS/2 Synaptics TouchPad" I have re-installed the operating system now twice after failed attempts to add the tapping option in the xorg configuration. The system wouldn't properly start after I have added the line to my configuration file in "/etc/X11/". I might have tried the wrong file but so far I was unable to find a specific Buster guide for this. The Debian Synaptics guide doesn't even mention Buster. Is it supposed to work on Buster out of the box and it doesn't because my hardware is really outdated now? | https://wiki.debian.org/LibinputTouchpad |
Code: Select all$ grep volume /etc/pulse/daemon.conf flat-volumes = no ; enable-deferred-volume = yes ; deferred-volume-safety-margin-usec = 8000 ; deferred-volume-extra-delay-usec = 0 ... yet audio volumes are low on vlc and web "apps" such as youtube and video servers when volume controls are maximized, along with Pulse Audio Volume Control. How to correct audio volumes in 10.x, please? | What does alsamixer show to you? |
Hi guys, For Debian Buster, is there a way to clear/empty my swap back to RAM again? I tried swapoff and swapon but it doesn't seem to work, it says command not found. I have the packages mount and util-linux. Any ideas? | Please explain better. Post exactly what commands you tried. Maybe http://forums.debian.net/viewtopic.php?f=16&t=142973 |
I just installed testing (Bullseye) and I've already messed up the sources.list. Code: Select alldavek@debian:~$ su Password: root@debian:/home/davek# apt update Hit:1 http://debian.osuosl.org/debian bullseye InRelease Ign:2 http://security.debian.org/debian-security bullseye/updates InRelease Err:3 http://security.debian.org/debian-security bullseye/updates Release 404 Not Found [IP: 2a04:4e42:d::204 80] Reading package lists... Done E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root@debian:/home/davek# here's my sources.list Code: Select all GNU nano 4.3 /etc/apt/sources.list # # deb cdrom:[Debian GNU/Linux testing _Bullseye_ - Official Snapshot amd64 DVD > #deb cdrom:[Debian GNU/Linux testing _Bullseye_ - Official Snapshot amd64 DVD B> deb http://debian.osuosl.org/debian/ bullseye main non-free deb-src http://debian.osuosl.org/debian/ bullseye main non-free # Line commented out by installer because it failed to verify: deb http://security.debian.org/debian-security bullseye/updates main contrib no> # Line commented out by installer because it failed to verify: deb-src http://security.debian.org/debian-security bullseye/updates main contri> How should it look. | Code: Select all deb http://debian.osuosl.org/debian/ bullseye main contrib non-free # deb-src http://debian.osuosl.org/debian/ bullseye main contrib non-free deb http://security.debian.org/debian-security bullseye/updates main contrib # deb-src http://security.debian.org/debian-security bullseye/updates main contrib Security repo may not be available for some time. |
Hi guys, I recently did a new install of Debian Buster, except reusing the /home partition, because I got a new motherboard+ram (i5-9400F/DDR4 2666Mhz from the old i5-2500k/DDR3 1333Mhz). I notice when I copy files, save files from Chromium/Firefox, or open files. There's some significant lag for some reason, no issues previously on Debian Stretch. I'm running i5-9400F 16GB RAM 8GB Swap 2TB Toshiba 7200rpm on EXT4 for both root and home partitions with a 500MB FAT Boot/EFI Nvidia GTX950 with nonfree Nvidia Drivers Debian Buster amd64 with Gnome 3.30.2 (wayland disappeared after a few days of use for some reason, can't find it in the login). Code: Select alltime ls Gives output for the home directory as: Code: Select allreal 0m0.004s user 0m0.001s sys 0m0.004s I did some googling and I deleted cache files (it was a few gigabytes in size) of the tracker and it helps slightly but I feel there's probably something I missed. Any ideas? | Head_on_a_Stick wrote:Do you still have this problem if you test with a new user and a clean ${HOME}? Sometimes old dot configs can cause problems. |
I'm currrently using Debian buster 64 bit. I'm testing nftables rules for my desktop. I want to add rules for TCP stealth scan and I got the following code from https://github.com/yoramvandevelde/nfta ... init.rules which gives the error Code: Select allnft add rule ip filter input iifname enp2s0 tcp flags & (ack|fin) == fin drop -bash: syntax error near unexpected token `==' but if I do the following code it gets accepted Code: Select allnft add rule inet filter input iifname enp2s0 tcp flags ack,fin,fin drop I also checked the ruleset Code: Select allroot@debian:~# nft list ruleset table inet filter { chain input { type filter hook input priority 0; policy drop; iifname "enp2s0" tcp flags != syn ct state new drop iifname "enp2s0" udp length { 28-32 } drop iifname "enp2s0" tcp flags fin,ack drop iifname "lo" ct state established,related accept iifname "enp2s0" ct state established,related accept iifname "enp2s0" ct state invalid,untracked drop } } How do i know if the code i added works; in Iptables i can always check with Code: Select all iptables -L -v what is the similar command for nftables? is my nftables rule for tcp stealth scan correct? P.S i checked the book Linux Firewalls ® Enhancing Security with nftables and Beyond fourth edition by Steve Suehring it only mentions TCP stealth scan rules for iptables only. | Lecram wrote:I'm currrently using Debian buster 64 bit. I'm testing nftables rules for my desktop. I want to add rules for TCP stealth scan and I got the following code from https://github.com/yoramvandevelde/nfta ... init.rules which gives the error Code: Select allnft add rule ip filter input iifname enp2s0 tcp flags & (ack|fin) == fin drop -bash: syntax error near unexpected token `==' Did you just run that script with bash or what? The page/file you linked tells you to: Code: Select allsudo nft -f nftables-init.rules What's the output of running that? (note also that you should NOT use that script as is.. but you probably know what you're doing do you? :) |
I'm using Debian stretch xfce 64 bit. I have a broadband connection. I'm using iptables as my firewall . When I ran a port scan through GRC Shields Up it shows only port 25 and port 80 are opened. I again ran the GRC shields up port scan with icmp disabled in the firewall and checked again but still it showed that port 25 and 80 were opened. I have also checked my adsl modem/router to see if it opens any port but i didn't find anything. These are my itable rules Code: Select all# Generated by iptables-save v1.6.0 on Sat Jul 13 18:34:36 2019 *filter :INPUT DROP [2:342] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] -A INPUT -s 10.0.0.0/8 -j DROP -A INPUT -s 169.254.0.0/16 -j DROP -A INPUT -s 172.16.0.0/12 -j DROP -A INPUT -s 127.0.0.0/8 -j DROP -A INPUT -s 192.168.0.0/24 -j DROP -A INPUT -s 224.0.0.0/4 -j DROP -A INPUT -d 224.0.0.0/4 -j DROP -A INPUT -s 240.0.0.0/5 -j DROP -A INPUT -d 240.0.0.0/5 -j DROP -A INPUT -s 0.0.0.0/8 -j DROP -A INPUT -d 0.0.0.0/8 -j DROP -A INPUT -d 239.255.255.0/24 -j DROP -A INPUT -d 255.255.255.255/32 -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,ACK -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP -A INPUT -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,RST FIN,RST -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,ACK FIN -j DROP -A INPUT -p tcp -m tcp --tcp-flags PSH,ACK PSH -j DROP -A INPUT -p tcp -m tcp --tcp-flags ACK,URG URG -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,PSH,ACK,URG -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,ACK,URG -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,PSH,URG -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN -j DROP -A INPUT -p tcp -m tcp --tcp-flags RST RST -j DROP -A INPUT -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -m conntrack --ctstate NEW -j DROP -A INPUT -p udp -m length --length 0:28 -j DROP -A INPUT -f -j DROP -A INPUT -i lo -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A INPUT -p tcp -m conntrack --ctstate NEW -m limit --limit 60/sec --limit-burst 30 -j ACCEPT -A INPUT -i enp2s0 -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i enp2s0 -p icmp -m icmp --icmp-type 3 -j ACCEPT -A INPUT -i enp2s0 -p icmp -m icmp --icmp-type 11 -j ACCEPT -A INPUT -i enp2s0 -p icmp -j DROP -A INPUT -m conntrack --ctstate INVALID,UNTRACKED -m limit --limit 2/min -j LOG --log-prefix "INVALID-INPUT: " --log-level 7 -A INPUT -m conntrack --ctstate INVALID,UNTRACKED -j DROP -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -m conntrack --ctstate INVALID,UNTRACKED -j DROP -A OUTPUT -o lo -m conntrack --ctstate ESTABLISHED -j ACCEPT -A OUTPUT -m conntrack --ctstate NEW,RELATED,ESTABLISHED -j ACCEPT -A OUTPUT -o enp2s0 -p tcp -m tcp --dport 53 ! --tcp-flags FIN,SYN,RST,ACK SYN -m conntrack --ctstate NEW -j ACCEPT -A OUTPUT -o enp2s0 -p udp -m conntrack --ctstate ESTABLISHED -m udp --dport 53 -j ACCEPT -A OUTPUT -o enp2s0 -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o enp2s0 -p icmp -m icmp --icmp-type 3 -j ACCEPT -A OUTPUT -o enp2s0 -p icmp -m icmp --icmp-type 11 -j ACCEPT -A OUTPUT -o enp2s0 -p icmp -j DROP -A OUTPUT -o enp2s0 -m conntrack --ctstate INVALID,UNTRACKED -m limit --limit 2/min -j LOG --log-prefix "INVALID-OUTPUT: " --log-level 7 -A OUTPUT -o enp2s0 -m conntrack --ctstate INVALID,UNTRACKED -j DROP COMMIT my iptables -L -v Code: Select alllec@debian:~$sudo iptables -L -v Chain INPUT (policy DROP 60 packets, 10320 bytes) pkts bytes target prot opt in out source destination 0 0 DROP all -- any any 10.0.0.0/8 anywhere 0 0 DROP all -- any any link-local/16 anywhere 0 0 DROP all -- any any 172.16.0.0/12 anywhere 12255 735K DROP all -- any any loopback/8 anywhere 0 0 DROP all -- any any 192.168.0.0/24 anywhere 0 0 DROP all -- any any base-address.mcast.net/4 anywhere 32 2693 DROP all -- any any anywhere base-address.mcast.net/4 0 0 DROP all -- any any 240.0.0.0/5 anywhere 0 0 DROP all -- any any anywhere 240.0.0.0/5 0 0 DROP all -- any any default/8 anywhere 0 0 DROP all -- any any anywhere default/8 0 0 DROP all -- any any anywhere 239.255.255.0/24 60 10320 DROP all -- any any anywhere 255.255.255.255 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST,ACK 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,SYN/FIN,SYN 0 0 DROP tcp -- any any anywhere anywhere tcp flags:SYN,RST/SYN,RST 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,RST/FIN,RST 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,ACK/FIN 0 0 DROP tcp -- any any anywhere anywhere tcp flags:PSH,ACK/PSH 0 0 DROP tcp -- any any anywhere anywhere tcp flags:ACK,URG/URG 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST,PSH,ACK,URG 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST,ACK,URG 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,PSH,URG 0 0 DROP tcp -- any any anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN 42 1692 DROP tcp -- any any anywhere anywhere tcp flags:RST/RST 0 0 DROP tcp -- any any anywhere anywhere tcp flags:!FIN,SYN,RST,ACK/SYN ctstate NEW 0 0 DROP udp -- any any anywhere anywhere length 0:28 0 0 DROP all -f any any anywhere anywhere 0 0 ACCEPT all -- lo any anywhere anywhere ctstate NEW,ESTABLISHED 6546 4570K ACCEPT all -- any any anywhere anywhere ctstate RELATED,ESTABLISHED 0 0 ACCEPT tcp -- any any anywhere anywhere ctstate NEW limit: avg 60/sec burst 30 0 0 ACCEPT icmp -- enp2s0 any anywhere anywhere icmp echo-reply 0 0 ACCEPT icmp -- enp2s0 any anywhere anywhere icmp destination-unreachable 0 0 ACCEPT icmp -- enp2s0 any anywhere anywhere icmp time-exceeded 0 0 DROP icmp -- enp2s0 any anywhere anywhere 0 0 LOG all -- any any anywhere anywhere ctstate INVALID,UNTRACKED limit: avg 2/min burst 5 LOG level debug prefix "INVALID-INPUT: " 0 0 DROP all -- any any anywhere anywhere ctstate INVALID,UNTRACKED Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- any any anywhere anywhere ctstate RELATED,ESTABLISHED 0 0 DROP all -- any any anywhere anywhere ctstate INVALID,UNTRACKED Chain OUTPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- any lo anywhere anywhere ctstate ESTABLISHED 18786 1674K ACCEPT all -- any any anywhere anywhere ctstate NEW,RELATED,ESTABLISHED 0 0 ACCEPT tcp -- any enp2s0 anywhere anywhere tcp dpt:domain flags:!FIN,SYN,RST,ACK/SYN ctstate NEW 0 0 ACCEPT udp -- any enp2s0 anywhere anywhere ctstate ESTABLISHED udp dpt:domain 0 0 ACCEPT icmp -- any enp2s0 anywhere anywhere icmp echo-request 0 0 ACCEPT icmp -- any enp2s0 anywhere anywhere icmp destination-unreachable 0 0 ACCEPT icmp -- any enp2s0 anywhere anywhere icmp time-exceeded 0 0 DROP icmp -- any enp2s0 anywhere anywhere 1 52 LOG all -- any enp2s0 anywhere anywhere ctstate INVALID,UNTRACKED limit: avg 2/min burst 5 LOG level debug prefix "INVALID-OUTPUT: " 1 52 DROP all -- any enp2s0 anywhere anywhere ctstate INVALID,UNTRACKED is there anything wrong in my iptables rule. Why does port 25 and 80 stay open? | I'm pretty sure GRC is just reporting your router configuration, NAT would prevent it from "seeing" your computer's ports. Try this Code: Select all# apt install nmap # nmap -sT -O localhost That should list all open ports. |
I installed OpenTK on .NET core. Worksgreat on Linux Mint 19. On Debian 10, I'm getting the following crash which complains about missing the shared library "gbm". Also, I found the libgdm project here (https://github.com/robclark/libgbm), but I'm not clear what Debian package I'm missing? I installed libgbm-dev which is the closest package, but that didn't contain libgbm.so Unhandled Exception: System.TypeInitializationException: The type initializer for 'OpenTK.DisplayDevice' threw an exception. ---> System.DllNotFoundException: Unable to load shared library 'gbm' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libgbm: cannot open shared object file: No such file or directory at OpenTK.Platform.Linux.Gbm.CreateDevice(Int32 fd) at OpenTK.Platform.Linux.LinuxFactory.SetupDisplay(String gpu, IntPtr& gbm_device, IntPtr& egl_display) at OpenTK.Platform.Linux.LinuxFactory.CreateDisplay(IntPtr& gbm_device, IntPtr& egl_display) at OpenTK.Platform.Linux.LinuxFactory.get_gpu_fd() at OpenTK.Platform.Linux.LinuxFactory.CreateDisplayDeviceDriver() at OpenTK.DisplayDevice..cctor() | You have written 3× libgdm and 3× libgbm. Debian has libopentk1.1-cil package. |
I installed Debian 10 Buster Non-Free MATE and am receiving the following error when trying to update: The repository 'http://debian.mirror.constant.com/debian buster/updates Release' does not have a Release file. What can i do to solve this problem? Thanks. | Try to edit /etc/apt/sources.list and replace Code: Select alldeb http://debian.mirror.constant.com/debian buster/updates mainbyCode: Select alldeb http://security.debian.org/debian-security buster/updates main |
Debian 9-stretch, recently upgraded from Debian 8-I'm getting ~20 lines of 'blk-update-request,i/o error,dev fd0,sector 0' messages on boot. I notice fd0 spinning on boot, there's obviously something trying to access it. Anyone know what file or program it might be? I looked at fstab but it's the same as my debian 8 install, on another partition, & that has no problem. | Do you have a floppy in the drive? Do you even use floppies? I leave the the drive unplugged in my old computer. |
Using Debian 10 MATE. I have a package locked in Synaptic under "Lock Version" but I am still getting updates for that package. There is an option in Package Updater to "Ignore this update" but it is grayed out. Is there a solution for this? Thanks. | What does mean Rick B. wrote:I am still getting updates for that package exactly? In aptitude, there are 2 options:aptitude help wrote:Hold a package in its current version to prevent upgrades. Keep a package at its current version. Unlike hold, this will not prevent future upgrades.You always get new update about available new version. But it will not be upgraded (in the first option), it will stay in old version... |
So lemme tell you a story, there was a bug with e2fsprog which needed logsave, untill new version came to repos manual fix was to install logsave and run update-initramfs which i did. Unfortunately this completely broke boot process for me, after choosing kernel it does' not prompt as usual for password but starts to message "volume group myvg not found, cannot process volume group myvg" and then goes to initramfs. Now new versions is already in repos, my sid is uptodate however 4.19.0-5 kernel still fails. Previous one works fine but i'd like to fix current one. Any suggestions what might it be? i've compared grub.cfg but it looks exactly the same for both kernels. | Pakos wrote:install logsave and run update-initramfs which i did. What kernel were you in when you rebuilt initramfs and were you at busy-box? What was your exact command. |
For solution - refer to http://forums.debian.net/viewtopic.php?f=16&t=142644 Folks, I am trying to selectively block applications' Internet access via apparmor. Testing it with Midori with the below apparmor profile Code: Select all# Last Modified: Wed Jul 10 09:17:35 2019 #include <tunables/global> /usr/bin/midori { #include <abstractions/base> #include <abstractions/evince> #include <abstractions/lightdm> #include <abstractions/nameservice> deny network inet raw, deny network inet6 raw, deny network inet stream, deny network inet6 stream, deny network inet dgram, deny network inet6 dgram, deny network, deny network inet stream, deny network inet6 stream, deny @{PROC}/[0-9]*/net/if_inet6 r, deny @{PROC}/[0-9]*/net/ipv6_route r, deny capability net_raw, deny @{PROC}/net/route r, /home/*/.Xauthority r, /home/*/.cache/gstreamer-1.0/registry.x86_64.bin r, /home/*/.cache/midori/** rw, /home/*/.cache/midori/web/1930540588 w, /home/*/.cache/midori/web/2068877454 w, /home/*/.cache/midori/web/2442868640 w, /home/*/.cache/midori/web/2709582449 w, /home/*/.cache/midori/web/2870961982 w, /home/*/.cache/midori/web/3123036655 w, /home/*/.cache/midori/web/3922757607 w, /home/*/.cache/midori/web/4225863230 w, /home/*/.cache/webkit/icondatabase/WebpageIcons.db rwk, /home/*/.config/dconf/user r, /home/*/.config/midori/ rw, /home/*/.config/midori/* rwk, /home/*/.config/midori/config.D9XL4Z rw, /home/*/.config/midori/history.db-shm rwk, /home/*/.config/midori/running w, /home/*/.config/midori/tabby.db-shm rwk, /home/*/.config/user-dirs.dirs r, /home/*/.local/share/gvfs-metadata/home r, /home/*/.local/share/gvfs-metadata/home-34641c3f.log r, /home/*/.local/share/gvfs-metadata/home-5166a826.log r, /home/*/.local/share/midori/apps/ r, /home/*/.local/share/midori/profiles/ r, /home/*/.local/share/webkit/databases/https_chicago.suntimes.com_0.localstorage w, /home/*/.local/share/webkit/databases/https_phonograph2.voxmedia.com_0.localstorage w, /home/*/.local/share/webkit/databases/https_secure-assets.rubiconproject.com_0.localstorage w, /home/*/.local/share/webkit/icondatabase/ r, /home/*/.local/share/webkit/icondatabase/WebpageIcons.db rwk, /home/*/.local/share/webkit/icondatabase/WebpageIcons.db-journal rw, /lib/x86_64-linux-gnu/ld-*.so mr, /{,var/}run/** mrwk, } as u can c i have added every possible deny network option, but it's still not working syslog excerpt below Code: Select allJul 10 10:34:27 debian apparmor[3420]: Reloading AppArmor profiles:. Jul 10 10:34:27 debian systemd[1]: Reloaded AppArmor initialization. Jul 10 10:34:36 debian kernel: [ 3996.072241] audit_printk_skb: 93 callbacks suppressed Jul 10 10:34:36 debian kernel: [ 3996.072242] audit: type=1400 audit(1562718876.939:278): apparmor="DENIED" operation="mkdir" profile="/usr/bin/midori" name="/home/a/.config/midori/extensions/libadblock.so/" pid=3521 comm="midori" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Jul 10 10:34:36 debian kernel: [ 3996.072264] audit: type=1400 audit(1562718876.939:279): apparmor="DENIED" operation="mkdir" profile="/usr/bin/midori" name="/home/a/.config/midori/extensions/libadblock.so/" pid=3521 comm="midori" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Jul 10 10:34:36 debian kernel: [ 3996.072276] audit: type=1400 audit(1562718876.939:280): apparmor="DENIED" operation="mkdir" profile="/usr/bin/midori" name="/home/a/.config/midori/extensions/libadblock.so/" pid=3521 comm="midori" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Jul 10 10:34:36 debian kernel: [ 3996.072290] audit: type=1400 audit(1562718876.939:281): apparmor="DENIED" operation="mkdir" profile="/usr/bin/midori" name="/home/a/.config/midori/extensions/libadblock.so/" pid=3521 comm="midori" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Jul 10 10:34:43 debian dbus-daemon[914]: Activating via systemd: service name='org.gnome.zeitgeist.Engine' unit='zeitgeist.service' Jul 10 10:34:43 debian systemd[897]: Starting Zeitgeist activity log service... Jul 10 10:34:43 debian zeitgeist-vacuu[3547]: zeitgeist-vacuum.vala:38: Impossible to open database `/home/a/.local/share/zeitgeist/activity.sqlite': unable to open database file Jul 10 10:34:43 debian systemd[897]: zeitgeist.service: Control process exited, code=exited status=14 Jul 10 10:34:43 debian systemd[897]: Failed to start Zeitgeist activity log service. Jul 10 10:34:43 debian systemd[897]: zeitgeist.service: Unit entered failed state. Jul 10 10:34:43 debian systemd[897]: zeitgeist.service: Failed with result 'exit-code'. Jul 10 10:34:43 debian kernel: [ 4002.305680] audit: type=1400 audit(1562718883.181:282): apparmor="DENIED" operation="mknod" profile="/usr/bin/midori" name="/home/a/.local/share/webkit/databases/https_en.wikipedia.org_0.localstorage" pid=3521 comm="midori" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Code: Select alla@debian:~$ lsb_release -da No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.9 (stretch) Release: 9.9 Codename: stretch anyone managed to get apparmor to block network? | https://unix.stackexchange.com/question ... y-apparmor |
Hi, I have a fresh Buster install that experiences connection issues to aus5.mozilla.org. This is the site that Firefox uses to check if an update is available. (I use the Firefox installed from http://www.mozilla.org tarball.) Currently Firefox does not update, because it is unable to connect to that site. If I try to visit https://aus5.mozilla.org in Firefox, it just gives the "Hmm. We’re having trouble finding that site." error. (The same happens with the debian-packaged Firefox ESR.) On a terminal, with netcat "nc -v aus5.mozilla.org 443" I get the error "nc: getaddrinfo for host "aus5.mozilla.org" port 443: Name or service not known". With "nc -4 -v aus5.mozilla.org 443" the connection succeeds. Possibly this has something to do with IPv6, since "host aus5.mozilla.org" returns: Code: Select allaus5.mozilla.org is an alias for balrog-aus5.r53-2.services.mozilla.com. balrog-aus5.r53-2.services.mozilla.com is an alias for balrog-aus5-noclip.r53-2.services.mozilla.com. balrog-aus5-noclip.r53-2.services.mozilla.com is an alias for balrog-cloudfront.prod.mozaws.net. balrog-cloudfront.prod.mozaws.net has address 13.32.43.24 balrog-cloudfront.prod.mozaws.net has address 13.32.43.17 balrog-cloudfront.prod.mozaws.net has address 13.32.43.39 balrog-cloudfront.prod.mozaws.net has address 13.32.43.107 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:400:a:db2a:b380:93a1 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:f800:a:db2a:b380:93a1 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:7600:a:db2a:b380:93a1 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:5e00:a:db2a:b380:93a1 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:8c00:a:db2a:b380:93a1 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:2800:a:db2a:b380:93a1 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:b000:a:db2a:b380:93a1 balrog-cloudfront.prod.mozaws.net has IPv6 address 2600:9000:2074:a800:a:db2a:b380:93a1 With "nc -v aus2.mozilla.org 443" the connection also succeeds. I don't need "-4" with that site. How can I fix my networking configuration? (The config is whatever is the default set up by Buster's installer.) I don't care about IPv6, since I cannot use it. | cchip wrote:I have a fresh Buster install that experiences connection issues to aus5.mozilla.org. This is the site that Firefox uses to check if an update is available. (I use the Firefox installed from http://www.mozilla.org tarball.) Where did you install your Firefox folder ? cchip wrote: The same happens with the debian-packaged Firefox ESR. Debian Firefox is updated by package update. No need to go to "aus5.mozilla.org" which is not supposed to be visited by the public. |
I am using Buster with MATE as a DE Trying to remove firefox-esr because I don't use it and this happens Code: Select allsudo apt remove firefox-esr [sudo] password for somebody: Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libjsoncpp1 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: bubblewrap epiphany-browser epiphany-browser-data evince evince-common gnome-desktop3-data libevdocument3-4 libevview3-3 libgnome-desktop-3-17 libgspell-1-1 libgspell-1-common libnautilus-extension1a libsynctex2 Suggested packages: nautilus-sendto unrar The following packages will be REMOVED: firefox-esr* The following NEW packages will be installed: bubblewrap epiphany-browser epiphany-browser-data evince evince-common gnome-desktop3-data libevdocument3-4 libevview3-3 libgnome-desktop-3-17 libgspell-1-1 libgspell-1-common libnautilus-extension1a libsynctex2 0 upgraded, 13 newly installed, 1 to remove and 0 not upgraded. Need to get 7,380 kB of archives. After this operation, 136 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. When I had Stretch this wasn't the case removing firefox-esr it would just uninstall and leave me alone so why is it any different in Buster? And why in the flying %$#@%^ would I need half of that stuff in the first place? This is not the only thing that has been forced upon me by Debian lately. It is really getting tiring and it reminds me of m$ forcing me to do this or that. Installing something else earlier and I had to remove 4 that I didn't ask for and weren't needed at all for the one I originally wanted. Yes I tried to do a search and got nothing but a bunch of unrelated crap no matter how I worded things trying to figure out how to get around this or why apt is doing it. I have always wondered why things have to be bundled in a package also(and I don't mean dependencies) instead of being able to chose that one app that I want to install or remove and not remove half of my OS with it. P.S. I don't want to just hide it from the menu I wanted to get rid of it before you mention doing so and it is already hidden. | http://forums.debian.net/viewtopic.php?f=16&t=104157 |
I have debian 9.6 stretch and I'm using LXDE desktop environment. I have my touchpad settings saved at /etc/X11/xorg.conf.d/50.synaptics.conf and when I restart lxde, touchpad settings are perfect, but as soon as I login touchpad is set back to previous state "as I hadn't configured /etc/X11/xorg.conf.d/50.synaptics.conf file at all". If I restart lxde, then touchpad settings are perfect again, but only at login screen. | Does the `synclient` command work after you've logged in? Perhaps libinput is used for the desktop. Have you checked the touchpad settings in LXDE?[1] Perhaps they are over-riding your configuration file. [1] If it has a GUI configuration tool for that; I don't use LXDE. |
Hello, when I switch to a virtual console and back to the desktop I experience trouble like diagonal lines on the desktop (like if the desktop was fragmented in triangles) that appear for an instant and then after a minute or so programs like firefox and konqueror start to crash and the next thing I know is that the desktop froze altogether and there is no way out but resettting the machine. Nvidia drivers from nonfree are installed for a geforce gt 630 card from my old pc running wheezy (it worked like a charm until the motherboard eventually died, I just passed to stretch on the new pc). The current machine is a brand new core i7/msi h110m pro-vh/kingston ssd and my 8 gb ram (2 sticks) tested fine in memtest. I believe there must be an issue with framebuffer, attempted to edit /etc/default/grub and reconfigure grub using Code: Select allGRUB_CMDLINE_LINUX_DEFAULT="vga=normal nofb nomodeset video=vesafb:off i915.modeset=0" GRUB_CMDLINE_LINUX="vga=normal nofb nomodeset video=vesafb:off i915.modeset=0" but only managed to see the boot messages (deleted "quiet" while being at that) and /dev/fb0 is still active, so the question is: can I disable framebuffer completely, and is this advisable ? I am at a loss now. | Oh for the days when we could control some sfuff.... If you look at the kernel version 4 and above command-line parameters https://www.kernel.org/doc/html/v4.14/a ... eters.html you'll only seeCode: Select allvga=still available from the list you posted, and vga=ask dosen't work, keep_bootcon didn't keep the bootcon at the frambuffer switch either, for me anyways.... fb0 is the kernels framebuffer of choice for screen, AFAICT.Code: Select all~# dmesg | grep -i vga This thread may or may not help for nvidia-settings and possible other clues. http://forums.debian.net/viewtopic.php?f=17&t=139043 framebuffer stuff - you have to find a flavor that suits your needs or roll your own. |
Hi There, I am trying to decrypt a root a partition which is spread on two disks through LVM using a key for the second drive. If I decrypt the disks manually the system is properly boot but with the key I can't because I didn't enable it properly. So far I saw since systemd the old debian script won't work anymore hence the only solution viable I found is creating hook (I hope): Code: Select allzless /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz 12. Storing keyfiles directly in the initrd ------------------------------------------- Normally devices using a keyfile are ignored (with a loud warning), and the key file itself is not included in the initrd, because the initramfs image typically lives on an unencrypted `/boot` partition. However in some cases it is desirable to include the key file in the initrd; for instance recent versions of GRUB support booting from encrypted block devices, allowing an encrypted `/boot` partition. Among the key files listed in the crypttab(5), those matching the value of the environment variable KEYFILE_PATTERN (interpreted as a shell pattern) will be included in the initramfs image. For instance if `/etc/crypttab` lists two key files `/etc/keys/{root,swap}.key`, you can add the following to `/etc/cryptsetup-initramfs/conf-hook` to add them to the initrd. KEYFILE_PATTERN="/etc/keys/*.key" Furthermore if the initramfs image is to include private key material, you'll want to create it with a restrictive umask in order to keep non-privileged users at bay. This can be achieved by adding the following to `/etc/initramfs-tools/initramfs.conf`. UMASK=0077 Unfortunaly I didn't understand what I should do exactly. I created a file inside the folder: /etc/cryptsetup-initramfs/conf-hook Code: Select allcrytpdata and I simply wrote: Code: Select allKEYFILE_PATTERN="/root/*.keyfile" I added the key on the crypttab and updated the initiramfs, but nothing happened. Probably I misunderstood the documentation. Can anyone help me? Thanks! | I found my issue I was been hours working on Code: Select all/etc/initramfs-tools/hooks convinced that was: Code: Select all /etc/cryptsetup-initramfs/conf-hook Oh man... |
Hi everyone, I am new on this forum. Nice to be here I have an issue with my remote server. It is hosted by 1&1 Ionos, using Parallels. When I first initialized it, the version was Stretch 9.9. Since I modified /etc/apt/source.list, updated and upgraded, I am no longer able to login using ssh. I have tried to find which package is responsible for this issue, but upgrading my system part by part, using apt-mark hold then unhold on some packages. It seems to be related to libc or locales, because before the following command I can login, and after I cannot: Code: Select all# apt-get install --only-upgrade locales Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libc-bin libc-dev-bin libc6 libc6-dev Suggested packages: glibc-doc manpages-dev Recommended packages: manpages manpages-dev libidn2-0 The following packages will be upgraded: libc-bin libc-dev-bin libc6 libc6-dev locales 5 upgraded, 0 newly installed, 0 to remove and 238 not upgraded. Need to get 10.7 MB of archives. After this operation, 12.3 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ftp.fr.debian.org/debian buster/main amd64 libc-dev-bin amd64 2.28-10 [275 kB] Get:2 http://ftp.fr.debian.org/debian buster/main amd64 libc6-dev amd64 2.28-10 [2691 kB] 30% [Working]debug2: channel 0: window 999390 sent adjust 49186 Get:3 http://ftp.fr.debian.org/debian buster/main amd64 locales all 2.28-10 [4060 kB] Get:4 http://ftp.fr.debian.org/debian buster/main amd64 libc6 amd64 2.28-10 [2867 kB] Get:5 http://ftp.fr.debian.org/debian buster/main amd64 libc-bin amd64 2.28-10 [789 kB] Fetched 10.7 MB in 1s (6302 kB/s) Preconfiguring packages ... (Reading database ... 19926 files and directories currently installed.) Preparing to unpack .../libc-dev-bin_2.28-10_amd64.deb ... Unpacking libc-dev-bin (2.28-10) over (2.24-11+deb9u4) ... Preparing to unpack .../libc6-dev_2.28-10_amd64.deb ... Unpacking libc6-dev:amd64 (2.28-10) over (2.24-11+deb9u4) ... Preparing to unpack .../locales_2.28-10_all.deb ... Unpacking locales (2.28-10) over (2.24-11+deb9u4) ... Preparing to unpack .../libc6_2.28-10_amd64.deb ... Checking for services that may need to be restarted... Checking init scripts... Unpacking libc6:amd64 (2.28-10) over (2.24-11+deb9u4) ... Setting up libc6:amd64 (2.28-10) ... Installing new version of config file /etc/ld.so.conf.d/x86_64-linux-gnu.conf ... Checking for services that may need to be restarted... Checking init scripts... Restarting services possibly affected by the upgrade: cron: restarting...done. Services restarted successfully. (Reading database ... 19994 files and directories currently installed.) Preparing to unpack .../libc-bin_2.28-10_amd64.deb ... Unpacking libc-bin (2.28-10) over (2.24-11+deb9u4) ... Setting up libc-bin (2.28-10) ... Updating /etc/nsswitch.conf to current default. Setting up libc-dev-bin (2.28-10) ... Setting up libc6-dev:amd64 (2.28-10) ... Setting up locales (2.28-10) ... Installing new version of config file /etc/locale.alias ... Generating locales (this might take a while)... Generation complete. The most interesting auth.log part I could find: Code: Select allJul 13 01:53:35 s22154214 sshd[12380]: fatal: ssh_sandbox_child: setrlimit(RLIMIT_FSIZE, { 0, 0 }): Function not implemented [preauth] Jul 13 01:53:41 s22154214 sshd[3622]: Received signal 15; terminating. Jul 13 01:53:41 s22154214 sshd[12508]: Server listening on 0.0.0.0 port 22. Jul 13 01:53:41 s22154214 sshd[12508]: Server listening on :: port 22. I am not really sure that it is the problem related to my login issue: I think this log was created when I tried to login, but I am trying to log again and again, I auth.log is no longer modified. Any idea what the problem could be? Thank you for your help! | I would be more interested to know what error message you get when you try logging in. I am no longer able to login using ssh. What does it say when you try ? If you can not log in to it via ssh, I don't see how you can repair anything or even access the logs as far as that goes, ...Do you have physical access to it ? There seems to be some missing info here, when I upgraded from Debian 9.8 to Buster, it did not affect my ssh access, How ever this error: Code: Select allfatal: ssh_sandbox_child: setrlimit(RLIMIT_FSIZE, { 0, 0 }): Function not implemented [preauth] Makes me think something really went wrong when you upgraded, maybe show us what your /etc/apt/sources.list file really has in it, if you can get that. Like the Gnome folks say "Oh no, something went wrong" ...What do we do now ? If it was me, I would contact the support people on your hosting , that is what they are for. ==== edited=== There is a very similar post here: https://serverfault.com/questions/92653 ... ng-sshd-toBut it is Ubuntooo, and a VM, is yours a VM as well, please give all the details you can think of. If it is a VM, what kind, EG: Qemu, VirtualBox, etc ? From your post: Code: Select allThe following packages will be upgraded: libc-bin libc-dev-bin libc6 libc6-dev locales 5 upgraded, 0 newly installed, 0 to remove and 238 not upgraded. 238 packages not upgraded, ? I don't think your upgrade was successfull |
I would appreciate any help regarding this issue o/ Yes yes I already did my homework but none of the solutions I found made any difference. I'm currently using a fresh install of Buster with Cinnamon both on my server and the local machine. The problem is none of the VNC servers are creating the xstartup file on the first run. When trying to connect remotely the result is a black screen with an message "could not acquire name on session bus" and in the log I found this error "cinnamon-session[1218]: WARNING: t+0,00730s: Failed to acquire org.gnome.SessionManager". After some research I found this bug on TigerVNC https://github.com/TigerVNC/tigervnc/issues/659. After some trying, I found out that TightVNC server creates an xstartup but it made no difference, the error persisted as described: Code: Select allunset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS exec cinnamon-session & Than I tried the solution on the link and manually copied the latest TigerVNC release and indeed it created a different xstartup file: Code: Select allunset SESSION_MANAGER unset DBUS_SESSION_BUS_ADDRESS OS=`uname -s` if [ $OS = 'Linux' ]; then case "$WINDOWMANAGER" in *gnome*) if [ -e /etc/SuSE-release ]; then PATH=$PATH:/opt/gnome/bin export PATH fi ;; esac fi if [ -x /etc/X11/xinit/xinitrc ]; then exec /etc/X11/xinit/xinitrc fi if [ -f /etc/X11/xinit/xinitrc ]; then exec sh /etc/X11/xinit/xinitrc fi [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & twm & Now There are no errors on the server log, but when connecting I still get only a black sceen with the the message "could not acquire name on session bus". So, any clues what I could try next??? | https://github.com/TurboVNC/turbovnc/issues/86 writes about Code: Select allTVNC_WM=mate-session, so I woud try Code: Select allTVNC_WM=cinnamon-session |
Debian 10 Buster. Acer Aspire V3-112P/R2 laptop. Using wifi at home, and a 3g dongle elsewhere. Orphaned wvdial worked in stretch, but could not get it to work in Buster, so I use ppp for 3g. But after 3g usage, boots are just PITA, so slow to bring wifi up. I use ifplugd, /etc/networking/interfaces: Code: Select allsource /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback allow-hotplug wlp2s0 iface wlp2s0 inet dhcp pre-up /usr/sbin/wpa_supplicant -iwlp2s0 -c/etc/wpa_supplicant/wpa_supplicant.conf gateway 192.168.1.1 nameserver 192.168.1.1. allow-hotplug enp3s0 iface enp3s0 inet dhcp Code: Select all[Starting] Restore /etc/resolv.conf if the system crashed before the ppp link was shut down [Starting] System Logging service... [Starting] Login Service... [Starting] Disk Manager [ OK ] Started Daily Rotation of log files [ OK ] Trigger anacron every hour [ OK ] Reached Target Timers [ OK ] D-Bus System Message Bus Starting LSB: Network connection manager... Starting WPA supplicant... [ OK ] Started System Logging service. [ OK ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down [ OK ] Started LSB: network connection manager. [ OK ] Started Initializing hardware monitoring sensors. [ OK ] Started WPA supplicant. Starting Authorization Manager... [ OK] Stared Authorization Manager. [ OK ] Started Login Service. [ OK ] Started Disk Manager. [ 11.266504] Bluetooth hci0: command 0x1000 tx timeout [ ***] A start job is running for Raise network interfaces (2 min 17 s / 5 min 2 s) /var/log/boot.log: (part) Code: Select allA start job is running for Raise network interfaces (6min 29s / 6min 32s) A start job is running for Raise network interfaces (6min 30s / 6min 32s) A start job is running for Raise network interfaces (6min 30s / 6min 32s) A start job is running for Raise network interfaces (6min 31s / 6min 32s) A start job is running for Raise network interfaces (6min 31s / 6min 32s) A start job is running for Raise network interfaces (6min 32s / 6min 32s) Failed to start Raise network interfaces See 'systemctl status networking.service' for details. Reached target Network. Reached target Network is Online. Starting LSB: Brings up/down network automatically... [ OK ] Started Permit User Sessions. Starting Hold until boot process finishes up... Starting Terminate Plymouth Boot Screen... #systemctl status networking.service Code: Select all● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese Active: failed (Result: timeout) since Sun 2019-07-14 15:12:55 EEST; 1h 1min Docs: man:interfaces(5) Process: 426 ExecStart=/sbin/ifup -a --read-environment (code=killed, signal=K Main PID: 426 (code=killed, signal=KILL) heinä 14 15:06:25 acer systemd[1]: Starting Raise network interfaces... heinä 14 15:06:25 acer ifup[426]: ifup: waiting for lock on /run/network/ifstate heinä 14 15:11:25 acer systemd[1]: networking.service: Start operation timed out heinä 14 15:11:25 acer ifup[426]: Got signal Terminated, terminating... heinä 14 15:12:55 acer systemd[1]: networking.service: State 'stop-sigterm' time heinä 14 15:12:55 acer systemd[1]: networking.service: Killing process 426 (ifup heinä 14 15:12:55 acer systemd[1]: networking.service: Main process exited, code heinä 14 15:12:55 acer systemd[1]: networking.service: Failed with result 'timeo heinä 14 15:12:55 acer systemd[1]: Failed to start Raise network interfaces. Purged resolvconf, but that had no effect. What would help? EDIT: fixed a few typos | A little progress. Shortened the timeout in /etc/systemd/system/network-online.target.wants/networking.service, which by default was 5 minutes Also some net search suggested removing allow-hotplug options from /etc/network/interfaces. Did that too. Now the boot time is tolerable, but I must start wpa_supplicant manually to get wifi working. |
After dist upgrading from Debian 9 (Stretch) to Debian 10 (Buster), my internal (secondary) SATA drive stopped working. Looks like there is some compatibility issue with Linux-4.19 which is the default kernel shipped with Buster. The drive is detected if I switch to Linux-4.09. For now defaulting to this in Grub. Anyone else facing this issue and has worked it out with Linux-4.19? | Did you follow the upgrade guide from the official Release Notes? Perhaps you made a mistake, boot a live ISO image and see if the drive is detected there. |
Hi, I'm running Debian Stretch recently installed, I cannot get my laptop resume after suspending, it seems like the suspend ends up shutting down the system. Here's what I could get from the logs but I don't know where to look next, any help would be appreciated... Before suspend: Code: Select allsystemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[5704]: Suspending system... (that's the last thing I found, then resume process) When trying to resume (it end up rebooting): Code: Select allkernel: PM: Checking hibernation image partition /dev/disk/by-uuid/92f30772-c8c5-4272-ad92-a5f6b32846d3 kernel: PM: Hibernation image not present or could not be loaded. kernel: PM: Starting manual resume from disk kernel: PM: Hibernation image partition 8:12 present kernel: PM: Looking for hibernation image. kernel: PM: Image not found (code -22) kernel: PM: Hibernation image not present or could not be loaded. System infos: Code: Select allLinux version 4.9.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) Hardware: Code: Select allH/W path Device Class Description ===================================================== system N501JW (ASUS-NotebookSKU) /0 bus N501JW /0/0 memory 64KiB BIOS /0/7 processor Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz /0/7/8 memory 1MiB L2 cache /0/7/9 memory 256KiB L1 cache /0/7/a memory 6MiB L3 cache /0/b memory 8GiB System Memory /0/b/0 memory 4GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/b/1 memory DIMM [empty] /0/b/2 memory 4GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/b/3 memory DIMM [empty] /0/100 bridge Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller /0/100/1 bridge Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller /0/100/1/0 display GM107M [GeForce GTX 960M] /0/100/2 display 4th Gen Core Processor Integrated Graphics Controller /0/100/3 multimedia Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller /0/100/14 bus 8 Series/C220 Series Chipset Family USB xHCI /0/100/14/0 usb3 bus xHCI Host Controller /0/100/14/0/1 input USB Receiver /0/100/14/0/5 communication Bluetooth wireless interface /0/100/14/0/7 multimedia USB2.0 HD UVC WebCam /0/100/14/0/a input SiS HID Touch Controller /0/100/14/1 usb4 bus xHCI Host Controller /0/100/16 communication 8 Series/C220 Series Chipset Family MEI Controller #1 /0/100/1a bus 8 Series/C220 Series Chipset Family USB EHCI #2 /0/100/1a/1 usb1 bus EHCI Host Controller /0/100/1a/1/1 bus USB hub /0/100/1b multimedia 8 Series/C220 Series Chipset High Definition Audio Controller /0/100/1c bridge 8 Series/C220 Series Chipset Family PCI Express Root Port #1 /0/100/1c.2 bridge 8 Series/C220 Series Chipset Family PCI Express Root Port #3 /0/100/1c.2/0 wlp59s0 network Wireless 7260 /0/100/1c.3 bridge 8 Series/C220 Series Chipset Family PCI Express Root Port #4 /0/100/1c.3/0 generic RTS5227 PCI Express Card Reader /0/100/1d bus 8 Series/C220 Series Chipset Family USB EHCI #1 /0/100/1d/1 usb2 bus EHCI Host Controller /0/100/1d/1/1 bus USB hub /0/100/1f bridge HM87 Express LPC Controller /0/100/1f.2 storage 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] /0/100/1f.3 bus 8 Series/C220 Series Chipset Family SMBus Controller /0/1 scsi4 storage [...] /0/1/0.0.0/7 /dev/sda7 volume 9537MiB EXT4 volume [...] /0/1/0.0.0/c /dev/sda12 volume 9536MiB Linux swap volume [...] /0/2 scsi5 storage [...] note: I added the swap uuid (and nokaslr because I found this in some previous posts...) in grub configuration: Code: Select all$ 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 nokaslr resume=/dev/disk/by-uuid/92f30772-c8c5-4272-ad92-a5f6b32846d3" 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" Thanks | How are you attempting to suspend? Why do the logs refer to hibernation instead? You should use /etc/initramfs-tools/conf.d/resume to set the resume device (and regenerate the initramfs afterwards) but that is for hibernation rather than suspend. Try the acpi_sleep= kernel parameter: https://askubuntu.com/questions/713805/ ... -power-off |
Hi to all, I am trying to figure out how to create a ipset set that will combine an individual IP & a network subnet. From man pages it should be: create blacklist4 hash:ip family inet hashsize 4096 maxelem 65536 add blacklist4 xxx.xxx.x.xxx add blacklist4 xx.xxx.xxx.0/24 Regards, t | tperica wrote:Hi to all, I am trying to figure out how to create a ipset set that will combine an individual IP & a network subnet. From man pages it should be: create blacklist4 hash:ip family inet hashsize 4096 maxelem 65536 add blacklist4 xxx.xxx.x.xxx add blacklist4 xx.xxx.xxx.0/24 Regards, t AFAIK with hash:ip you can only have individual IPs (that's what I use for fail2ban). You can create a table with hash:net (like "create netblock hash:net family inet hashsize 8192 maxelem 65536"), which will work with networks (like "add netblock 185.211.247.0/24") I use hash:net for manual backlists (like example above). If you want BOTH I guess you must use hash:net and add "1.2.3.4/32", etc. |
In general, I been having some issues with mounting devices (SATA drives connected via USB docing station - Unitek, for example) on boot up. So here's the thing, I have read that if you want to ensure that a drive is mounted consistently, its better to use the UUID opposed it's device name (/dev/sdb1 for example). That (for me) has not been the case. From what I have experienced, a soft boot (more often than not) will not always mount the device as I wish it to be mounted. On the other-hand, a hard boot will (more often than not) mount the devices correctly. It does not appear to matter when using UUID or device name, miss-mounting happens more often that I wish it to. Is there any certain way to lock in a device name on either warm/cold boot that will remain consistent? Thanks all, C | Head_on_a_Stick wrote:cds60601 wrote:I have read that if you want to ensure that a drive is mounted consistently, its better to use the UUID opposed it's device name (/dev/sdb1 for example). ^ This is correct, the block devices are assigned dynamically and may change from one boot to the next. I prefer PARTUUIDs, which stay the same even if the partition is reformatted That is what I appeared to be not using. I did this for the SATA drive I have inplace of my CD/DVD burner in a laptop. After about a dozen reboots (both warm and cold), this particular drive has held firm. Perfecto!!! here are the lines (old and new) below. Code: Select all#/dev/sdb1 /media/work ext4 defaults,nofail,x-systemd.device-timeout=10000ms 0 2 PARTUUID=b12723ad-4ba3-de47-884b-ea1926d2f2e3 /media/work ext4 defaults,nofail,x-systemd.device-timeout=10000ms 0 2 The next issue to correct was to do the same with 2 LUKS drives. Below is the current entries in /etc/fstab Code: Select all/dev/mapper/xa /media/xa ext4 defaults,nofail 0 0 /dev/mapper/xb /media/xb ext4 defaults,nofail 0 0 This seems to be correct, but what I did find out, is that using cryptsetup luksDump, I should have had the UUID in /etc/crypttab. Below reflects old and new entries. Code: Select all#xa /dev/sdc1 /root/xdky luks noauto #xb /dev/sdd1 /root/xdky luks noauto xa UUID=27ecc87f-7f6c-4953-9f9f-356b5e27b6fa /root/xdky luks xb UUID=49dba909-4db0-4066-8473-1389d951c15a /root/xdky luks So, thanks in part to HoaS and a little more investigating, I think I solved the original problems!!! Gladly will take any advice on entries to either file mentioned above. C |
I am not really a Linux newbie but again there is a lot I don’t know or understand or know very little about. Using Buster wtih KDE (when I installed the OS I chose no DE then in temrinal did apt install kde-plasma-desktop to get minimal KDE without all the bloat and crap I don't want need or use) but I had this same thing happen using Stretch a few months ago also which was setup identical to the way I have Buster setup now. This is my trouble I have my machine setup to have a static IP and I use a custom(?? not sure if that's the proper wording) DNS. Every once in a while my resolv.conf will change to my ISP DNS by itself. Never have a problem between my machine and router I can always connect to the router and internet. I don’t use a network manager because I don’t have a need to since my wifi on this machine doesn’t work anymore(not sure why but not really important to me since I don’t take it anywhere) /etc/resolv.conf Code: Select all nameserver xxx.xxx.xx.xxx nameserver xxx.xxx.xx.xxx nameserver xxx.xxx.xx.xxx nameserver xxx.xxx.xx.xxx nameserver xxx.xxx.xx.xxx options rotate /etc/network/interfaces Code: Select all The loopback network interface auto lo iface lo inet loopback The primary network interface allow-hotplug enp3s0 iface enp3s0 inet static address xxx.xxx.x.x gateway xxx.xxx.x.x ifconfig Code: Select all enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet xxx.xxx.x.x netmask xxx.xxx.xxx.x broadcast xxx.xxx.x.xxx inet6 xxxx::xxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20 ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet) RX packets 3367 bytes 3214013 (3.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2875 bytes 391854 (382.6 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 loop txqueuelen 1000 (Local Loopback) RX packets 813 bytes 298711 (291.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 813 bytes 298711 (291.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Is there something I did wrong or I am missing that may cause this? The OS tells me I have no DHCP services even installed so I don’t think that is it though I could be wrong. I set this all up after reading documentation right from Debian (the wiki and other resources on the website). If there is any missing information that may be needed to help just say so and I will post back with it Thanks for reading my novel of a post LoL. EDIT: Of course it just dawned on me that the DHCP in my router could be the culprit. Problem with killing that is I have 2 windows machines on my network(my gf and my daughter) that just don't want to run with a static ip for some reason. Would setting resolv.conf to read only stop that or cause problems elsewhere? | Set it in /etc/dhcp/dhclient.conf. Here's mine for OpenDNS and a couple of others as fallback: Code: Select allsupersede domain-name-servers 208.67.222.222,208.67.220.220,1.1.1.1,8.8.8.8; I just added that line to the end of the file. |
Hi, I'm on Stretch (Gnome) trying to change the default app to common Office extensions to Libreoffice 6.2. So I added /usr/share/applications/defaults.list and in it: Code: Select all[Default Applications] application/msword=libreoffice6.2-writer.desktop application/vnd.openxmlformats-officedocument.wordprocessingml.document=libreoffice6.2-writer.desktop application/vnd.oasis.opendocument.text=libreoffice6.2-writer.desktop application/vnd.ms-excel=libreoffice6.2-calc.desktop application/vnd.openxmlformats-officedocument.spreadsheetml.sheet=libreoffice6.2-calc.desktop application/vnd.oasis.opendocument.spreadsheet=libreoffice6.2-calc.desktop Only .doc files have correctly switched to LO 6.2, all the others stay by default with LO 5. Why? | nutagape wrote: And if I right click a document file -> open with different application -> select the desired app, there's no "set as default" button. right click file - properties - open with tab |
Hi, I receive this ERROR: crc32 mismatch in command when I was restoring a system backup with btrfs send/receive .. I applied this.: http://forums.debian.net/viewtopic.php?f=16&t=142344 For Backup: - Debian 9 - btrfs-progs (4.13.3-1~bpo9+1) sudo btrfs send -v /.snapshots/3/snapshot/ |pv -s 14G| split -b 1000M --filter 'lzop -1 > "$FILE.lzo"' For Restoring : - Debian 10 (Livecd) - btrfs-progs (4.20.1-2:) cat xa* | lzop -dN --ignore-warn |pv -s 14G| sudo btrfs receive /media/sda3/rootsys ----------------------------------- After that I was able to restore with errors the backup by using ( btrfs receive --max-errors 0) and boot the system without apparently anything broken.: cat xa* | lzop -dN --ignore-warn |pv -s 14G| sudo btrfs receive -v --max-errors 0 /media/sda3/rootsys It showed a lot of errors type.: ERROR: rename 0-2323.23.. -> root/.local failed: Directory not empty, here you can see a capture.: So, Now, do I have my system corrupted?.. Do I need to use same btrfs-progs version to restore woth success?..Whats was the problem? | I checked the system, and everything seems to work.. I deleted all empty inode folders created by ERRORs btrfs receive. Thanks to God, I didnt lost my system ..Ive no external disk and have to play with left space in partitions to make theses kind of experiments |
Hello there, I really appreciate if some can help me configuring a wireless device, I have already followed Debian's documentation and instructions in multiple forums but it is not working yet I have installed Debian 9 in a laptop HP Pavilion 13 an0012la(https://support.hp.com/us-en/document/c06209147) and it has the wireless device Intel Wireless-AC 9461. I have installed firmware-iwlwifi from backports but there is no wireless interface available yet. I also installed packages firmware-linux, firmware-misc-nonfree and intel-microcode but it is still not working. The laptop has Windows 10 Home 64 installed and Wifi works properly there, so I can guess the wireless device is not broken. Next are some commands and their outputs. There is no interface available: Code: Select all> ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 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 > iwconfig lo no wireless extensions. The firmware is installed: Code: Select all> apt policy firmware-iwlwifi firmware-iwlwifi: Installed: 20190114-1~bpo9+2 Candidate: 20190114-1~bpo9+2 Version table: *** 20190114-1~bpo9+2 100 100 /var/lib/dpkg/status The iwlwifi module is loaded: Code: Select all> lsmod | grep iwl iwlwifi 151552 0 cfg80211 589824 1 iwlwifi I see the device but there is no kernel drive in use for it: Code: Select all> lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0b) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3ea0] Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 0b) Subsystem: Hewlett-Packard Company Skylake Processor Thermal Subsystem [103c:84c5] Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:9df9] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:9ded] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Device [8086:9def] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:14.3 Network controller [0280]: Intel Corporation Device [8086:9df0] (rev 30) Subsystem: Intel Corporation Device [8086:0264] 00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:9de8] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:16.0 Communication controller [0780]: Intel Corporation Device [8086:9de0] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:9dd3] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] Kernel driver in use: ahci Kernel modules: ahci 00:19.0 Serial bus controller [0c80]: Intel Corporation Device [8086:9dc5] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9db0] (rev f0) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.1 PCI bridge [0604]: Intel Corporation Device [8086:9db1] (rev f0) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.4 PCI bridge [0604]: Intel Corporation Device [8086:9db4] (rev f0) Kernel driver in use: pcieport Kernel modules: shpchp 00:1e.0 Communication controller [0780]: Intel Corporation Device [8086:9da8] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:1e.2 Serial bus controller [0c80]: Intel Corporation Device [8086:9daa] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d84] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9dc8] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:9da3] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:9da4] (rev 30) Subsystem: Hewlett-Packard Company Device [103c:84c5] 07:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:0113] (rev 01) Subsystem: Toshiba America Info Systems Device [1179:0001] Kernel driver in use: nvme Kernel modules: nvme There is no log messages for iwlwifi: Code: Select all> dmesg | grep iwl There is nothing really useful in logs about wireless or wifi: Code: Select all> dmesg | grep -i wireless -A2 [ 2.019518] Intel(R) Wireless WiFi driver for Linux [ 2.019519] Copyright(c) 2003- 2015 Intel Corporation [ 2.087076] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYSBUS:00/PNP0C0D:00/input/input3 -- [ 2.090925] input: HP Wireless hotkeys as /devices/virtual/input/input6 [ 2.093630] tsc: Refined TSC clocksource calibration: 1800.034 MHz [ 2.093643] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x19f2498a886, max_idle_ns: 440795202126 ns > dmesg | grep -i wifi -A2 [ 2.019518] Intel(R) Wireless WiFi driver for Linux [ 2.019519] Copyright(c) 2003- 2015 Intel Corporation [ 2.087076] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYSBUS:00/PNP0C0D:00/input/input3 Nothing here: Code: Select all> rfkill list all Kernel version: Code: Select all> uname -r 4.9.0-9-amd64 Could please any one give me some guide about what else I can try to fix it? In advance, thanks! Carlos | You should install the backport kernel too |
Hello I'm trying to set up a new laptop with an Intel 9260 wifi card. It's a clean and upgrade debian installation. I've installed firmware-iwlwifi from stable and backport and none of them worked. I downloaded firmware from intel, i copied it into /lib/firmware/. I've tried every solution I've found. But nothings works. Some system info: Code: Select allroot@paxila:~# uname -a Linux paxila 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64 GNU/Linux Code: Select alllspci -k .... 01:00.0 Network controller: Intel Corporation Device 2526 (rev 29) Subsystem: Intel Corporation Device 0014 .... Code: Select allroot@paxila:~# modinfo iwlwifi | grep iwlwifi filename: /lib/modules/4.9.0-9-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko firmware: iwlwifi-100-5.ucode firmware: iwlwifi-1000-5.ucode firmware: iwlwifi-135-6.ucode firmware: iwlwifi-105-6.ucode firmware: iwlwifi-2030-6.ucode firmware: iwlwifi-2000-6.ucode firmware: iwlwifi-5150-2.ucode firmware: iwlwifi-5000-5.ucode firmware: iwlwifi-6000g2b-6.ucode firmware: iwlwifi-6000g2a-6.ucode firmware: iwlwifi-6050-5.ucode firmware: iwlwifi-6000-4.ucode firmware: iwlwifi-7265D-26.ucode firmware: iwlwifi-7265-17.ucode firmware: iwlwifi-3168-26.ucode firmware: iwlwifi-3160-17.ucode firmware: iwlwifi-7260-17.ucode firmware: iwlwifi-8265-26.ucode firmware: iwlwifi-8000C-26.ucode firmware: iwlwifi-9000-pu-a0-lc-a0--26.ucode firmware: iwlwifi-9260-th-a0-jf-a0--26.ucode firmware: iwlwifi-9000-pu-a0-jf-a0--26.ucode firmware: iwlwifi-Qu-a0-jf-b0--26.ucode Code: Select allroot@paxila:~# ls /lib/firmware/iwlwifi-9* /lib/firmware/iwlwifi-9260-th-b0-jf-b0-33.ucode /lib/firmware/iwlwifi-9260-th-b0-jf-b0-41.ucode /lib/firmware/iwlwifi-9260-th-b0-jf-b0-34.ucode /lib/firmware/iwlwifi-9260-th-b0-jf-b0-43.ucode /lib/firmware/iwlwifi-9260-th-b0-jf-b0-38.ucode /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode I can only make it working following this link: https://wireless.wiki.kernel.org/en/use ... components But it says: If you use a well known distribution If you use a well maintained distribution, your device should be supported out of the box. If your device doesn't work at all (you can't even see it in the interface list), then it might mean that your kernel is too old or that you don't have the proper firmware. You can contact your distribution to have them fix this. In the meantime, you can use the backport tree to make your device work. ... Is there any bug with kernel or firmware packages? Thanks! David Pérez | Following https://wireless.wiki.kernel.org/en/use ... components I can see on dmesg: Code: Select alladministrador@paxila:~$ sudo dmesg | grep iwlwifi [ 2.585436] Loading modules backported from iwlwifi [ 2.585437] iwlwifi-stack-public:master:7858:cb17257d [ 2.650290] iwlwifi 0000:01:00.0: firmware: failed to load iwl-dbg-cfg.ini (-2) [ 2.650291] iwlwifi 0000:01:00.0: Direct firmware load for iwl-dbg-cfg.ini failed with error -2 [ 2.654645] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-9260-th-b0-jf-b0-46.ucode [ 2.654878] iwlwifi 0000:01:00.0: loaded firmware version 46.3cfab8da.0 op_mode iwlmvm [ 2.730130] iwlwifi 0000:01:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [ 2.777852] iwlwifi 0000:01:00.0: base HW address: 98:3b:8f:c2:14:fb [ 2.856667] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0 But I can't see 5GHz network and bluetooth is not working. |
I am using Stretch + backports, up to date. Printer is Brother HL -2270DW. Printer connected directly to computer It was working perfectly but all of a sudden it crashes computer completely, turns it off, after sending a print job. I am at my wits end with this, please help | I would start by looking at the cups log files in /var/log/cups/error.log. I don't use cups much but my web search indicated that the log files can get really large. If the files exceed the allocated disk space, it can core dump. |
I am to following the instructions from kernel-team.pages.debian.net/kernel-handbook, Chapter 4, section 2. Ultimately my goal is to build the psmouse.ko kernel module, but first I would like to build the kernel as well. I'm running "Buster" uname - r returns 4.19.0-5-amd64 From section 4.2.1 I execute: $ apt-get source linux After that, I took a look in my /home directory and found a directory called: linux-4.19.37 I was expecting 4.19.0, but got 4.19.37? Is this going to be a problem, especially if I build a module using the headers from this version? I also tried: $ apt-get source linux=$(uname -r), It said "Skipping already downloaded file 'linux_4.19.37-3.dsc'" and two similar messages. Here is my /etc/apt/sources.list deb http://deb.debian.org/debian buster main contrib non-free deb-src http://deb.debian.org/debian buster main contrib non-free deb http://security.debian.org/debian-security buster/updates main contrib non-free deb-src http://security.debian.org/debian-security buster/updates main contrib non-free deb http://deb.debian.org/debian buster-updates main contrib non-free deb-src http://deb.debian.org/debian buster-updates main contrib non-free Any help is greatly appreciated, thank you! | LateToTheGame wrote:I was expecting 4.19.0, but got 4.19.37? Is this going to be a problem, especially if I build a module using the headers from this version? Nope - they're both 4.19 kernels but one has had 37 patches applied to it. Kernel version is the same |
Hello, I just upgraded my laptop from stretch to buster via a wireless connection to my router. As soon as the upgrade was through, the wifi stopped to work. A reboot did not rectify the issue. NetworkManager shows the wifi as connected. It has received an IP address via dhcp and set the route properly. But then it just stops to allow packages to go through. Wireshark on another computer connected to the same network shows that there are arp requests from the laptop, which are answered by the router - but they do not seem to get to the laptop. This only happens with the wireless connection. When I use a cable to connect to the router I get connected and everything works as expected. Is this a bug - or am I missing something? Code: Select all># lspci 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01) ># lsmod | grep rt rtl8188ee 106496 0 rtl_pci 36864 1 rtl8188ee rtlwifi 98304 2 rtl_pci,rtl8188ee mac80211 815104 3 rtl_pci,rtl8188ee,rtlwifi cfg80211 761856 2 rtlwifi,mac80211 ># ip a s 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: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether a0:1d:48:d1:4f:99 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 34:23:87:29:31:cb brd ff:ff:ff:ff:ff:ff inet 192.168.2.10/24 brd 192.168.2.255 scope global dynamic noprefixroute wlan0 valid_lft 42831sec preferred_lft 42831sec inet6 fe80::62c8:b264:b3dd:2b4e/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: virbr3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:ba:dd:ff brd ff:ff:ff:ff:ff:ff inet 192.168.100.1/24 brd 192.168.100.255 scope global virbr3 valid_lft forever preferred_lft forever 5: virbr3-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr3 state DOWN group default qlen 1000 link/ether 52:54:00:ba:dd:ff brd ff:ff:ff:ff:ff:ff ># ip r s default via 192.168.2.253 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.10 metric 600 192.168.100.0/24 dev virbr3 proto kernel scope link src 192.168.100.1 linkdown ># arp Address HWtype HWaddress Flags Mask Iface _gateway (incomplete) wlan0 192.168.2.6 (incomplete) wlan0 ># iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination | Have you installed firmware-misc-nonfree? |
Installed Debian yesterday and have had a pleasant experience except for my inability to get the Wired Connection working. I have a Wireless connection that connects and allows me to access Internet. The Wired connection activates, but does not have any Internet. I installed network-manager in hopes that it would do something. This computer dual boots with Windows 10, where it is able to establish an Ethernet connection, so I know it's not a cable issue. Code: Select allip a (when I am connected to both wireless and wired) 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 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,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 54:a0:50:88:02:67 brd ff:ff:ff:ff:ff:ff inet6 2601:410:4200:1490:3db7:b480:c149:bae3/64 scope global temporary dynamic valid_lft 212562sec preferred_lft 85850sec inet6 2601:410:4200:1490:56a0:50ff:fe88:267/64 scope global mngtmpaddr noprefixroute dynamic valid_lft 212562sec preferred_lft 212562sec inet6 fe80::56a0:50ff:fe88:267/64 scope link valid_lft forever preferred_lft forever 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether dc:85:de:cb:f4:13 brd ff:ff:ff:ff:ff:ff inet 192.168.0.19/24 brd 192.168.0.255 scope global dynamic wlp3s0 valid_lft 85510sec preferred_lft 85510sec inet6 2601:410:4200:1490:ae2d:d92b:d52e:bc36/64 scope global noprefixroute dynamic valid_lft 212562sec preferred_lft 212562sec inet6 fe80::750d:dee3:cc5c:1169/64 scope link valid_lft forever preferred_lft forever Noticed that the eno1 is missing an IPv4 address. Also tried tweaking files in Code: Select all cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback Code: Select all cat /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp One thing that I noticed so far is that my Ethernet is called eth0 in interfaces.d, while it's called eno1 from ip a. I tried to update the etho0 to eno1 and then restart the service, but was not successful. From my understanding of network-manager, the interfaces file should be ignored now? Code: Select allcat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile [ifupdown] managed=true When I try to ping anything on the Wired connection Code: Select all ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1): 56 data bytes ping: sending packet: Network is unreachable Code: Select allping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: sending packet: Network is unreachable Any help would be appreciated! | Did you try to select "Require IPv4 addressing for this connection to complete" in nm-connection-editor? |
Hi all, I have an external wireless network adapter that I plugged it to my Asus laptop. That's name is tp-link and its model is TL-WN725N. I renamed it by moving forward by this link: https://www.itzgeek.com/how-tos/linux/d ... ian-9.html but after reboot, its name changed to wlan0. While I would like to change its name to something like tplink-wnic. Any input would be appreciated. Thanks | create file /etc/systemd/network/10-TL-WN725N.link Code: Select all[Match] MACAddress=00:86:ea:b5:03:63 <-- your MAC [Link] Name=tplink-wnic Code: Select all#update-initramfs -u and reboot Undo whatever that link told you to do. |
So I installed stable Buster using Guided partitioning with encrypted LVM and instead of getting the grub wallpaper I get a blue screen with cyan text. sudo update-grub Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-4.19.0-5-amd64 Found initrd image: /boot/initrd.img-4.19.0-5-amd64 Adding boot menu entry for EFI firmware configuration done using grub-efi-amd64 /etc/default/grub Code: Select all# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Code: Select allcat /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod lvm insmod ext2 set root='lvmid/9ugOIn-3x05-Jd8l-rXMX-yxWd-geZ5-6wEf43/TC21gk-FHYo-pDe4-dblY-iHJ4-mrOW-lQFdVj' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='lvmid/9ugOIn-3x05-Jd8l-rXMX-yxWd-geZ5-6wEf43/TC21gk-FHYo-pDe4-dblY-iHJ4-mrOW-lQFdVj' af80b53f-9509-42b7-a2c7-fc8e59d22e69 else search --no-floppy --fs-uuid --set=root af80b53f-9509-42b7-a2c7-fc8e59d22e69 fi font="/usr/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_US insmod gettext fi terminal_output gfxterm if [ "${recordfail}" = 1 ] ; then set timeout=30 else if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### insmod lvm insmod ext2 set root='lvmid/9ugOIn-3x05-Jd8l-rXMX-yxWd-geZ5-6wEf43/TC21gk-FHYo-pDe4-dblY-iHJ4-mrOW-lQFdVj' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='lvmid/9ugOIn-3x05-Jd8l-rXMX-yxWd-geZ5-6wEf43/TC21gk-FHYo-pDe4-dblY-iHJ4-mrOW-lQFdVj' af80b53f-9509-42b7-a2c7-fc8e59d22e69 else search --no-floppy --fs-uuid --set=root af80b53f-9509-42b7-a2c7-fc8e59d22e69 fi insmod png if background_image /usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then set color_normal=white/black set color_highlight=black/white else set menu_color_normal=cyan/blue set menu_color_highlight=white/blue fi ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload="${1}" } set linux_gfx_mode= export linux_gfx_mode menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-af80b53f-9509-42b7-a2c7-fc8e59d22e69' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 e97b0516-2554-4bce-9573-2d5191d4d477 else search --no-floppy --fs-uuid --set=root e97b0516-2554-4bce-9573-2d5191d4d477 fi echo 'Loading Linux 4.19.0-5-amd64 ...' linux /vmlinuz-4.19.0-5-amd64 root=/dev/mapper/debian--vg-root ro quiet echo 'Loading initial ramdisk ...' initrd /initrd.img-4.19.0-5-amd64 } submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-af80b53f-9509-42b7-a2c7-fc8e59d22e69' { menuentry 'Debian GNU/Linux, with Linux 4.19.0-5-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-5-amd64-advanced-af80b53f-9509-42b7-a2c7-fc8e59d22e69' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 e97b0516-2554-4bce-9573-2d5191d4d477 else search --no-floppy --fs-uuid --set=root e97b0516-2554-4bce-9573-2d5191d4d477 fi echo 'Loading Linux 4.19.0-5-amd64 ...' linux /vmlinuz-4.19.0-5-amd64 root=/dev/mapper/debian--vg-root ro quiet echo 'Loading initial ramdisk ...' initrd /initrd.img-4.19.0-5-amd64 } menuentry 'Debian GNU/Linux, with Linux 4.19.0-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-5-amd64-recovery-af80b53f-9509-42b7-a2c7-fc8e59d22e69' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 e97b0516-2554-4bce-9573-2d5191d4d477 else search --no-floppy --fs-uuid --set=root e97b0516-2554-4bce-9573-2d5191d4d477 fi echo 'Loading Linux 4.19.0-5-amd64 ...' linux /vmlinuz-4.19.0-5-amd64 root=/dev/mapper/debian--vg-root ro single echo 'Loading initial ramdisk ...' initrd /initrd.img-4.19.0-5-amd64 } } ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/30_uefi-firmware ### menuentry 'System setup' $menuentry_id_option 'uefi-firmware' { fwsetup } ### END /etc/grub.d/30_uefi-firmware ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### Code: Select allcat 05_debian_theme #!/bin/sh set -e # grub-mkconfig helper script. # Copyright (C) 2010 Alexander Kurtz <kurtz.alex@googlemail.com> # # GRUB is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # GRUB is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with GRUB. If not, see <http://www.gnu.org/licenses/>. # Include the GRUB helper library for grub-mkconfig. . /usr/share/grub/grub-mkconfig_lib # We want to work in /boot/grub/ only. test -d /boot/grub; cd /boot/grub # Set the location of a possibly necessary cache file for the background image. # NOTE: This MUST BE A DOTFILE to avoid confusing it with user-defined images. BACKGROUND_CACHE=".background_cache" set_default_theme(){ case $GRUB_DISTRIBUTOR in Tanglu|Ubuntu|Kubuntu) # Set a monochromatic theme for Tanglu/Ubuntu. echo "${1}set menu_color_normal=white/black" echo "${1}set menu_color_highlight=black/light-gray" if [ -e /usr/share/plymouth/themes/default.grub ]; then sed "s/^/${1}/" /usr/share/plymouth/themes/default.grub fi # For plymouth backward compatiblity. Can be removed # after xenial. if [ -e /lib/plymouth/themes/default.grub ]; then sed "s/^/${1}/" /lib/plymouth/themes/default.grub fi ;; *) # Set the traditional Debian blue theme. echo "${1}set menu_color_normal=cyan/blue" echo "${1}set menu_color_highlight=white/blue" ;; esac } module_available(){ local module for module in "${1}.mod" */"${1}.mod"; do if [ -f "${module}" ]; then return 0 fi done return 1 } set_background_image(){ # Step #1: Search all available output modes ... local output for output in ${GRUB_TERMINAL_OUTPUT}; do if [ "x$output" = "xgfxterm" ]; then break fi done # ... and check if we are able to display a background image at all. if ! [ "x${output}" = "xgfxterm" ]; then return 1 fi # Step #2: Check if the specified background image exists. if ! [ -f "${1}" ]; then return 2 fi # Step #3: Search the correct GRUB module for our background image. local reader case "${1}" in *.jpg|*.JPG|*.jpeg|*.JPEG) reader="jpeg";; *.png|*.PNG) reader="png";; *.tga|*.TGA) reader="tga";; *) return 3;; # Unknown image type. esac # Step #4: Check if the necessary GRUB module is available. if ! module_available "${reader}"; then return 4 fi # Step #5: Check if GRUB can read the background image directly. # If so, we can remove the cache file (if any). Otherwise the backgound # image needs to be cached under /boot/grub/. if is_path_readable_by_grub "${1}"; then rm --force "${BACKGROUND_CACHE}.jpeg" \ "${BACKGROUND_CACHE}.png" "${BACKGROUND_CACHE}.tga" elif cp "${1}" "${BACKGROUND_CACHE}.${reader}"; then set -- "${BACKGROUND_CACHE}.${reader}" "${2}" "${3}" else return 5 fi # Step #6: Prepare GRUB to read the background image. if ! prepare_grub_to_access_device "`${grub_probe} --target=device "${1}"`"; then return 6 fi # Step #7: Everything went fine, print out a message to stderr ... echo "Found background image: ${1}" >&2 # ... and write our configuration snippet to stdout. Use the colors # desktop-base specified. If we're using a user-defined background, use # the default colors since we've got no idea how the image looks like. # If loading the background image fails, use the default theme. echo "insmod ${reader}" echo "if background_image `make_system_path_relative_to_its_root "${1}"`; then" if [ -n "${2}" ]; then echo " set color_normal=${2}" fi if [ -n "${3}" ]; then echo " set color_highlight=${3}" fi if [ -z "${2}" ] && [ -z "${3}" ]; then echo " true" fi echo "else" set_default_theme " " echo "fi" } # Earlier versions of grub-pc copied the default background image to /boot/grub # during postinst. Remove those obsolete images if they haven't been touched by # the user. They are still available under /usr/share/images/desktop-base/ if # desktop-base is installed. while read checksum background; do if [ -f "${background}" ] && [ "x`sha1sum "${background}"`" = "x${checksum} ${background}" ]; then echo "Removing old background image: ${background}" >&2 rm "${background}" fi done <<EOF 648ee65dd0c157a69b019a5372cbcfea4fc754a5 debian-blueish-wallpaper-640x480.png 0431e97a6c661084c59676c4baeeb8c2f602edb8 debian-blueish-wallpaper-640x480.png 968ecf6696c5638cfe80e8e70aba239526270864 debian-blueish-wallpaper-640x480.tga 11143e8c92a073401de0b0fd42d0c052af4ccd9b moreblue-orbit-grub.png d00d5e505ab63f2d53fa880bfac447e2d3bb197c moreblue-orbit-grub.png f5b12c1009ec0a3b029185f6b66cd0d7e5611019 moreblue-orbit-grub.png EOF # Include the configuration of desktop-base if available. if [ -f "/usr/share/desktop-base/grub_background.sh" ]; then . "/usr/share/desktop-base/grub_background.sh" fi # First check whether the user has specified a background image explicitly. # If so, try to use it. Don't try the other possibilities in that case # (#608263). if [ -n "${GRUB_BACKGROUND+x}" ]; then set_background_image "${GRUB_BACKGROUND}" || set_default_theme exit 0 fi # Next search for pictures the user put into /boot/grub/ and use the first one. for background in *.jpg *.JPG *.jpeg *.JPEG *.png *.PNG *.tga *.TGA; do if set_background_image "${background}"; then exit 0 fi done # Next try to use the background image and colors specified by desktop-base. if set_background_image "${WALLPAPER}" "${COLOR_NORMAL}" "${COLOR_HIGHLIGHT}"; then exit 0 fi # If we haven't found a background image yet, use the default from desktop-base. case $GRUB_DISTRIBUTOR in Ubuntu|Kubuntu) ;; Tanglu) if set_background_image "/usr/share/images/grub/grub.png"; then exit 0 fi ;; *) if set_background_image "/usr/share/images/desktop-base/desktop-grub.png"; then exit 0 fi ;; esac # Finally, if all of the above fails, use the default theme. set_default_theme The grub settings are from the default install with Gnome desktop from tasksel. Why is this happening? | soaringowl2145 wrote:Found background image: /usr/share/images/desktop-base/desktop-grub.png This is not accessible until after decryption, move it to /boot/somewhere would be my guess, never tried it... |
Debian/jessie-I have gnome/xfce/kde desktops & only gnome has the login sound. Anyone know the procedure for getting same in xfce or kde? I do have sound in xfce & kde just no login sound. | UbuntuForums.org: How to correctly enable the Login sound in Xubuntu 16.04 and new versions |
Hi, Exec Summary after net install (with no desktop environment) -> install xorg + display manager + window manager of choice. The keyboard configuration in /etc/default/keyboard is not being honoured. Am I unique in this aspect? Any help in understanding why and correcting the issue would be appreciated. Description Laptop, Macbook pro 11,2 (late 2012) With the release of buster I thought I'd try it out (having successfully installed and configured sid 3-4 months ago). My install process was to grab the net install iso, burn to usb and install. I'm in the uk so (carefully) selected all the gb locale options and the installation proceeded without a hitch. (I say "carefully" because I went through the install twice just in case I made a mistake) First issue is that if I do a `dpkg-reconfigure -plow keyboard-configuration` the list presented is not in english (google suggests either russian, french, dutch or afrikaans when I try to translate the various options) - I have to alter the command to `LC_ALL=C dpkg-reconfigure -plow keyboard-configuration` in order for it to be english. Looking at my `locale`, it's all `en_GB.UTF-8` which seems correct and is the same as my older SID install. I just use a window manager so installed `xorg,xorg-dev` + my window manager (dwm). This also goes ok. My keyboard at this point is gb english - fine for my usb plugin keyboard but not for the actual mac layout. Second issue I therefore changed `/etc/default/keyboard` as follows: Code: Select allXKBLAYOUT="gb" BACKSPACE="guess" XKBMODEL="pc105" XKBVARIANT="mac" XKBOPTIONS="" followed by a `systemctl restart keyboard-setup.service`. This did not change the layout, I tried a re-boot, the layout still did not change. I tried `dpkg-reconfigure` for the keyboard and console. I reinstalled `keyboard-configuration`. Still no joy (rebooting in-between). I tried just changing to us layout (i.e. `XKBLAYOUT="us"` and`XKBVARIANT=""`) but still no change. Has anyone else come across this? I don't see it mentioned on the forum, but then maybe my searching skills are poor. . I'm at work at the moment so will action any requests for further information later in the day if it requires terminal output. Any suggestions would be greatly appreciated. Most puzzling (at least for me) Kind Regards Rob | What does this say: Code: Select allLC_ALL=C localectl |
I am using vbox and everything was OK until last night. I cannot start windows virtual machine, I get an error message that vboxdrv is not loaded. If I try to load the kernel module with modprobe I get this "modprobe: ERROR: could not insert 'vboxdrv': Invalid argument". I don't know whats wrong. | Update. dmesg shows this errors: Code: Select all[ 26.267359] vboxdrv: loading out-of-tree module taints kernel. [ 26.267808] vboxdrv: disagrees about version of symbol cpu_tlbstate [ 26.267811] vboxdrv: Unknown symbol cpu_tlbstate (err -22) [ 160.745876] vboxdrv: disagrees about version of symbol cpu_tlbstate [ 160.745879] vboxdrv: Unknown symbol cpu_tlbstate (err -22) [ 2256.973850] vboxdrv: disagrees about version of symbol cpu_tlbstate [ 2256.973854] vboxdrv: Unknown symbol cpu_tlbstate (err -22) |
I recently moved my old server disk to new hardware. On the newly installed system (stretch) only one of the disks was correctly detected at boot, the other one showed no partitions at all. After several different approaches (fdisk, parted, testdisk), all of them showing a working GPT with no problems, I was only able to solve the problem by placing "partx" in rc.local to add the partition after boot. Any idea why partx finds the partitions and the normal startup process doesn't? Both disks are 8TB seagate archive disks, albeit not bought at the same time, with EXT4. The only irregularity is a warning in dmesg that the problem disks partition is not zone aligned: dmesg: [ 500.912595] sde: sde1 [ 500.912611] sde: p1 start 2048+15628051080 is not zone aligned As I understand it, misalignment could only result in a slight performance hit? Could this be the reason? Edit: [SOLVED] I use shingled drives, which have to be zone-aligned starting with Linux 4.10. See the post below. Now that I know the solution, I have found someone with the same problem and even almost the same drive constellation: Partitioning the ST8000AS0022 also describes how to correctly align the partition. Cheers, Tony | alfauriga wrote:the other one showed no partitions at all. After several different approaches (fdisk, parted, testdisk), all of them showing a working GPT with no problems These two statements seem to contradict each other. What do you mean by "show" ? Please show us instead of telling what you see. |
I'd like to implement the following iptables rule in nftables but don't know how to do it. Code: Select all$ iptables -t mangle -A FORWARD -o enp1s0 \ -p tcp -m tcp --tcp-flags SYN,RST SYN \ -s 192.168.2.0/24 \ -m tcpmss --mss 1361:1536 \ -j TCPMSS --set-mss 1360 Explanation: For packets with source IP in the address range 192.168.2.0/24 forwarded to enp1s0, set the MSS of TCP SYN packets to 1360 only for those with MSS greater than 1361 and less than 1536. The nftables.conf that I'd like to modify: Code: Select allflush ruleset # ----- IPv4 ONLY ----- # filter table ip filter { chain input { type filter hook input priority 0; policy accept; } chain output { type filter hook output priority 0; policy accept; counter comment "count accepted packets" } chain forward { type filter hook forward priority 0; policy accept; counter comment "count dropped packets" } } table ip nat { chain prerouting { type nat hook prerouting priority 0; } chain postrouting { type nat hook postrouting priority 100; ip saddr 192.168.2.0/24 oifname enp1s0 masquerade } } # ----- IPv6 ----- # Block all IPv6 traffic. table ip6 filter { chain input { type filter hook input priority 0; reject } chain output { type filter hook output priority 0; reject } chain forward { type filter hook forward priority 0; reject } } Any help appreciated. Thanks. | Got it, you chance the forward chain in the ip filter table to: Code: Select all chain forward { type filter hook forward priority 0; policy accept; ip saddr 192.168.2.0/24 oifname enp1s0 tcp flags syn tcp option maxseg size set 1360 counter comment "count dropped packets" } Then if you execute: Code: Select all$ echo 1 >/proc/sys/net/ipv4/ip_no_pmtu_disc Your TCP and UDP packet sizes will never exceed the interface MTU. Happy days. |
I am using Debian 9.8.0 amd64. I need to install the libgs-dev package for compiling ImageMagick on my Debian machine. When I run the following command: Code: Select allsudo apt-get install libgs-dev The following errors are produced. Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgs-dev : Depends: libijs-dev but it is not installable Depends: libjbig2dec0-dev but it is not installable Depends: libpaper-dev but it is not installable E: Unable to correct problems, you have held broken packages. How can I install the libgs-dev package on my Debian machine? | It, and all it’s dependencies, are available from the stable repo. Resolving your issue will depend on how you fucked up your system to start with. |
Hi everybody, I'm using debian testing and until now I've been using gnome-disks tool, to automatically mount a ntfs partition on my second HD that I use to store static data (documents, music, films,...) Since now, I will be able to both view and write content in that partition but now i'm unable to write any content on it (I'm still being able to see all the data) using Nemo 3.2.2. ntfs-3g package is already installed. Here is my gnome-disk configuration (click to enlarge) Current Permissions: Code: Select allnolddor@computer:~$ ls -lia /mnt total 16 786433 drwxr-xr-x 3 root root 4096 ene 11 17:32 . 2 drwxr-xr-x 22 root root 4096 abr 28 11:36 .. 5 drwxrwxrwx 1 root root 8192 abr 7 16:21 sdb This is the output of df -h command: Code: Select allS.ficheros Tamaño Usados Disp Uso% Montado en udev 7,8G 0 7,8G 0% /dev tmpfs 1,6G 9,3M 1,6G 1% /run /dev/sda5 61G 54G 3,5G 95% / tmpfs 7,8G 137M 7,7G 2% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 7,8G 0 7,8G 0% /sys/fs/cgroup /dev/sda2 96M 26M 71M 28% /boot/efi /dev/sdb 466G 325G 142G 70% /mnt/sdb <------------ This is the mounted partition tmpfs 1,6G 36K 1,6G 1% /run/user/1000 Output of fdisk -l Code: Select allDisco /dev/sdb: 465,8 GiB, 500107862016 bytes, 976773168 sectores Unidades: sectores de 1 * 512 = 512 bytes Tamaño de sector (lógico/físico): 512 bytes / 4096 bytes Tamaño de E/S (mínimo/óptimo): 4096 bytes / 4096 bytes Tipo de etiqueta de disco: dos Identificador del disco: 0x72706d6f Disposit. Inicio Comienzo Final Sectores Tamaño Id Tipo /dev/sdb1 539915109 2359355303 1819440195 867,6G 7 HPFS/NTFS/exFAT /dev/sdb2 1634738290 3549463011 1914724722 913G 2b desconocido /dev/sdb3 1811941901 2356117036 544175136 259,5G 63 GNU HURD o SysV /dev/sdb4 2643197962 2643247798 49837 24,3M 61 SpeedStor La partición 1 no empieza en el límite del sector físico. La partición 2 no empieza en el límite del sector físico. La partición 3 no empieza en el límite del sector físico. La partición 4 no empieza en el límite del sector físico. Disco /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 sectores Unidades: sectores de 1 * 512 = 512 bytes Tamaño de sector (lógico/físico): 512 bytes / 512 bytes Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes Tipo de etiqueta de disco: gpt Identificador del disco: 9E45210A-C07D-4F11-9BA1-C69C1A39481C Disposit. Comienzo Final Sectores Tamaño Tipo /dev/sda1 2048 1023999 1021952 499M Entorno de recuperación de Windows /dev/sda2 1024000 1228799 204800 100M Sistema EFI /dev/sda3 1228800 1261567 32768 16M Reservado para Microsoft /dev/sda4 1261568 325599231 324337664 154,7G Datos básicos de Microsoft /dev/sda5 325599232 455112703 129513472 61,8G Sistema de ficheros de Linux /dev/sda6 455112704 488396799 33284096 15,9G Linux swap Any help? | nolddor wrote:Since now, I will be able to both view and write content in that partition Do you mean "until now I was able to both view and write contents" ? nolddor wrote:but now i'm unable to write any content on it using Nemo Can you show evidence (error message...) ? Did you try from the console ? Did you check whether the filesystem is mounted read-write or read-only ? Code: Select allmount | grep sdb nolddor wrote:Do you mind to explain me what uid,gid,umask and fmask values are? Code: Select allman ntfs-3g |
Happy Star Wars day everyone. I'm having trouble with a fresh postfix + spamassassin + dovecot +amavis install on Debian Stretch. Incoming mail is hung up in the queue with a "mail transport unavailable" error, until I manually run "postsuper -r ALL && postfix flush". The only clue that anything is wrong is this error in mail.warn: Code: Select allmail postfix/qmgr[16088]: warning: connect to transport private/spamassassin: No such file or directory So I'm sure this is the culprit. I just have no idea what file/directory it's complaining about not being able to access. When I do flush the queue, spamassassin does it's job, and things are being properly filtered. Here is my master.cf: https://pastebin.com/H7D50YpL Output of ps aux | grep spam: Code: Select allroot 16928 0.2 4.4 172448 90464 ? Ss 22:31 0:01 /usr/bin/perl -T -w /usr/sbin/spamd -d --pidfile=/var/run/spamd.pid --create-prefs --max-children 5 --helper-home-dir root 16929 0.0 4.7 179560 97432 ? S 22:31 0:00 spamd child root 16930 0.0 4.7 179748 95952 ? S 22:31 0:00 spamd child postfix 17079 0.1 0.4 106972 10068 ? S 22:43 0:00 smtpd -n smtp -t inet -u -c -o stress= -v -o content_filter=spamassassin postfix 17082 0.1 0.4 106832 10036 ? S 22:44 0:00 smtpd -n smtp -t inet -u -c -o stress= -v -o content_filter=spamassassin According to this article https://www.binarytides.com/install-spa ... x-dovecot/, when I run "netstat -nlp4 | grep spam" I should see spamc listening at 127.0.0.1:738, but I don't get anything listening on that port at all. Although a "sudo netstat -l4 | grep spam" does return this: Code: Select alltcp 0 0 localhost:spamd 0.0.0.0:* LISTEN Again, I'm sure spamassassin is holding up the show here. Any suggestions are appreciated. Thanks! | So it turns out that I needed to create a spamassassin directory under /var/spool/postfix/private. Things are running smoothly now. |
Found my solution on https://askubuntu.com/questions/892026/ ... ity-server. OS: Debian Stretch 9.9 stretch Kernel: x86_64 Linux 4.19.0-0.bpo.4-amd64 | Without additional details about your system (kernel version, Debian version etc.) none of the visitors of this forum will help you. |
EDIT: . The members of this forum just helped me fix and repair a nasty hard disk error. I had run file system checks before, but what I never knew was that the default check does not update the bad block inode list. p.H wrote:e2fsck detects and marks bad blocks only when run with the -c option. With that one sentence, p.H saved my computer. And the advice that he and L_V gave me in this thread was priceless. What ultimately worked for me was checking both my / (root) and /home partitions with the non-destructive read-write option, -cc from a Live CD: Code: Select alle2fsck -f -y -cc -C0 /dev/sda5 e2fsck -f -y -cc -C0 /dev/sda7 That check identified and repaired the affected inodes. It also wrote over the damaged files. Keep a list of those files. You will have to replace them (as explained below). Next, I ran the checks again with the read-only option -c: Code: Select alle2fsck -f -y -c -C0 /dev/sda5 e2fsck -f -y -c -C0 /dev/sda7 Running the check a second time was an important step because it added a few more blocks to the bad blocks list. Having repaired the file system, the next step was to repair the affected files: p.H wrote:Note that e2fsck can remap bad blocks but cannot restore the unreadable contents of the affected files, so these files must be reinstalled from their respective packages. In my case, I had a fresh install of Debian Buster and a Debian Buster Live CD, so I just copied them from the Live CD: Code: Select allmkdir /media/inspiron mount /dev/sda5 /media/inspiron cp /usr/bin/$FILE01 /media/inspiron/usr/bin/$FILE01 cp /usr/bin/$FILE02 /media/inspiron/usr/bin/$FILE02 ... umount /dev/sda5 After that, the computer booted like a charm. Importantly, it shutdown like a charm too. There were no priority 0 or 1 messages in my journalctl. Thank you to p.H and L_V for helping me rescue this old machine! . ---------------------------------------- ORIGINAL POST: After a fresh installation of Debian Buster on an old machine, the partition that contains my /home partition does not unmount at shutdown. The problem seems to be caused by an I/O error. At first glance, smartctl does not show any errors, but a deeper looks shows that the disk experienced a few errors on the / (root) partition a few years ago. If I followed Linux Admins' "Fixing disk problems" guide would that resolve the issue? Thanks in advance, - Soul Code: Select all$ journalctl -r -b -1 -p3 -- Logs begin at Sun 2019-05-19 13:22:05 EDT, end at Sun 2019-05-19 15:26:53 EDT. -- May 19 14:51:02 inspiron systemd[1]: Failed unmounting /home. May 19 14:51:02 inspiron kernel: print_req_error: I/O error, dev sda, sector 162964427 May 19 14:51:02 inspiron kernel: ata1.00: error: { UNC } May 19 14:51:02 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 14:51:02 inspiron kernel: ata1.00: cmd 60/08:88:c8:a3:b6/00:00:09:00:00/40 tag 17 ncq dma 4096 in res 41/40:08:cb:a3:b6/00:00:09:00:00/00 Emask 0x409 (media error) <F> May 19 14:51:02 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 14:51:02 inspiron kernel: ata1.00: irq_stat 0x40000008 May 19 14:51:02 inspiron kernel: ata1.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 May 19 14:50:59 inspiron kernel: print_req_error: I/O error, dev sda, sector 162964427 May 19 14:50:59 inspiron kernel: ata1.00: error: { UNC } May 19 14:50:59 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 14:50:59 inspiron kernel: ata1.00: cmd 60/20:a8:c0:a3:b6/00:00:09:00:00/40 tag 21 ncq dma 16384 in res 41/40:20:cb:a3:b6/00:00:09:00:00/00 Emask 0x409 (media error) <F> May 19 14:50:59 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 14:50:59 inspiron kernel: ata1.00: irq_stat 0x40000008 May 19 14:50:59 inspiron kernel: ata1.00: exception Emask 0x0 SAct 0x200000 SErr 0x0 action 0x0 May 19 14:50:43 inspiron wpa_supplicant[509]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/1 May 19 14:47:06 inspiron root[7585]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 14:40:19 inspiron root[7277]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 14:34:55 inspiron root[7129]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 14:27:20 inspiron root[6970]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 14:19:26 inspiron root[6425]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 14:13:30 inspiron root[6164]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 14:07:00 inspiron root[4631]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 14:01:11 inspiron root[3004]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 13:53:40 inspiron root[2451]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 13:46:29 inspiron root[2355]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 13:41:26 inspiron root[2260]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 13:33:31 inspiron root[1803]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 13:28:13 inspiron root[1633]: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1 May 19 13:26:48 inspiron kernel: print_req_error: I/O error, dev sda, sector 201851126 May 19 13:26:48 inspiron kernel: ata1.00: error: { UNC } May 19 13:26:48 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:48 inspiron kernel: ata1.00: cmd 60/08:c8:f0:00:08/00:00:0c:00:00/40 tag 25 ncq dma 4096 in res 41/40:08:f6:00:08/00:00:0c:00:00/00 Emask 0x409 (media error) <F> May 19 13:26:48 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:48 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:48 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:48 inspiron kernel: ata1.00: cmd 60/08:98:90:f6:3c/00:00:0a:00:00/40 tag 19 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:48 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:48 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:48 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:48 inspiron kernel: ata1.00: cmd 60/08:90:08:3e:d1/00:00:30:00:00/40 tag 18 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:48 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:48 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:48 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:48 inspiron kernel: ata1.00: cmd 60/08:88:08:2d:8d/00:00:15:00:00/40 tag 17 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:48 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:48 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:48 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:48 inspiron kernel: ata1.00: cmd 60/08:80:c0:3e:59/00:00:09:00:00/40 tag 16 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:48 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:48 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:48 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:48 inspiron kernel: ata1.00: cmd 61/18:30:18:7f:c5/00:00:2f:00:00/40 tag 6 ncq dma 12288 out res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:48 inspiron kernel: ata1.00: failed command: WRITE FPDMA QUEUED May 19 13:26:48 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:48 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:48 inspiron kernel: ata1.00: cmd 60/08:28:c8:6a:71/00:00:15:00:00/40 tag 5 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:48 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:48 inspiron kernel: ata1.00: irq_stat 0x40000001 May 19 13:26:48 inspiron kernel: ata1.00: exception Emask 0x0 SAct 0x20f0060 SErr 0x0 action 0x0 May 19 13:26:45 inspiron kernel: print_req_error: I/O error, dev sda, sector 361573512 May 19 13:26:45 inspiron kernel: print_req_error: I/O error, dev sda, sector 156843584 May 19 13:26:45 inspiron kernel: print_req_error: I/O error, dev sda, sector 201851126 May 19 13:26:45 inspiron kernel: print_req_error: I/O error, dev sda, sector 359754432 May 19 13:26:45 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:45 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:45 inspiron kernel: ata1.00: cmd 60/d0:f0:88:2c:8d/00:00:15:00:00/40 tag 30 ncq dma 106496 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:45 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:45 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:45 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:45 inspiron kernel: ata1.00: cmd 60/00:e8:40:3e:59/01:00:09:00:00/40 tag 29 ncq dma 131072 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:45 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:45 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:45 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:45 inspiron kernel: ata1.00: cmd 60/08:58:08:3e:d1/00:00:30:00:00/40 tag 11 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:45 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:45 inspiron kernel: ata1.00: error: { UNC } May 19 13:26:45 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:45 inspiron kernel: ata1.00: cmd 60/08:48:f0:00:08/00:00:0c:00:00/40 tag 9 ncq dma 4096 in res 41/40:08:f6:00:08/00:00:0c:00:00/00 Emask 0x409 (media error) <F> May 19 13:26:45 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:45 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:45 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:45 inspiron kernel: ata1.00: cmd 60/08:18:90:f6:3c/00:00:0a:00:00/40 tag 3 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:45 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:45 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:45 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:45 inspiron kernel: ata1.00: cmd 60/40:10:c0:6a:71/00:00:15:00:00/40 tag 2 ncq dma 32768 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:45 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:45 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:45 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:45 inspiron kernel: ata1.00: cmd 61/08:00:00:70:cc/00:00:31:00:00/40 tag 0 ncq dma 4096 out res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:45 inspiron kernel: ata1.00: failed command: WRITE FPDMA QUEUED May 19 13:26:45 inspiron kernel: ata1.00: irq_stat 0x40000001 May 19 13:26:45 inspiron kernel: ata1.00: exception Emask 0x0 SAct 0x60000a0d SErr 0x0 action 0x0 May 19 13:26:40 inspiron kernel: print_req_error: I/O error, dev sda, sector 804169080 May 19 13:26:40 inspiron kernel: print_req_error: I/O error, dev sda, sector 361572440 May 19 13:26:40 inspiron kernel: print_req_error: I/O error, dev sda, sector 201851904 May 19 13:26:40 inspiron kernel: print_req_error: I/O error, dev sda, sector 201851126 May 19 13:26:40 inspiron kernel: print_req_error: I/O error, dev sda, sector 813441024 May 19 13:26:40 inspiron kernel: print_req_error: I/O error, dev sda, sector 201848320 May 19 13:26:39 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/40:e0:78:a5:ee/00:00:2f:00:00/40 tag 28 ncq dma 32768 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/08:c8:30:59:d1/00:00:30:00:00/40 tag 25 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/08:c0:58:60:92/00:00:31:00:00/40 tag 24 ncq dma 4096 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/58:60:58:28:8d/00:00:15:00:00/40 tag 12 ncq dma 45056 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/d8:58:00:04:08/06:00:0c:00:00/40 tag 11 ncq dma 897024 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: error: { UNC } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/00:50:00:00:08/04:00:0c:00:00/40 tag 10 ncq dma 524288 in res 41/40:00:f6:00:08/00:04:0c:00:00/00 Emask 0x409 (media error) <F> May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/40:48:00:20:7c/00:00:30:00:00/40 tag 9 ncq dma 32768 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: error: { ABRT } May 19 13:26:39 inspiron kernel: ata1.00: status: { DRDY ERR } May 19 13:26:39 inspiron kernel: ata1.00: cmd 60/00:40:00:f6:07/06:00:0c:00:00/40 tag 8 ncq dma 786432 in res 41/04:00:f6:00:08/00:00:0c:00:00/00 Emask 0x1 (device error) May 19 13:26:39 inspiron kernel: ata1.00: failed command: READ FPDMA QUEUED May 19 13:26:39 inspiron kernel: ata1.00: irq_stat 0x40000001 May 19 13:26:39 inspiron kernel: ata1.00: exception Emask 0x0 SAct 0x13001f00 SErr 0x0 action 0x0 May 19 13:22:09 inspiron kernel: mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: FW version command failed -5 May 19 13:22:09 inspiron kernel: mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: Could not read FW version May 19 13:22:05 inspiron kernel: ACPI: SPCR: Unexpected SPCR Access Width. Defaulting to byte size Code: Select all# fdisk -l Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: ST9500325AS Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x07f2837e Device Boot Start End Sectors Size Id Type /dev/sda1 63 208844 208782 102M de Dell Utility /dev/sda2 * 208845 30928844 30720000 14.7G 7 HPFS/NTFS/exFAT /dev/sda3 30928845 155775023 124846179 59.5G 7 HPFS/NTFS/exFAT /dev/sda4 155782305 976768064 820985760 391.5G 5 Extended /dev/sda5 * 155782368 177305599 21523232 10.3G 83 Linux /dev/sda6 177307648 199903231 22595584 10.8G 82 Linux swap / Solaris /dev/sda7 199905280 976766975 776861696 370.4G 83 Linux Code: Select all# smartctl -l selftest /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-5-amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 0 - Code: Select all# smartctl -a /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-5-amd64] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Momentus 5400.6 Device Model: ST9500325AS Serial Number: 6VEGMVRP LU WWN Device Id: 5 000c50 03067dd6f Firmware Version: D005DEM1 User Capacity: 500,107,862,016 bytes [500 GB] Sector Size: 512 bytes logical/physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Sun May 19 15:05:07 2019 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 139) minutes. Conveyance self-test routine recommended polling time: ( 3) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 101 089 006 Pre-fail Always - 29958806 3 Spin_Up_Time 0x0003 099 099 085 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 091 091 020 Old_age Always - 9917 5 Reallocated_Sector_Ct 0x0033 088 088 036 Pre-fail Always - 246 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 207791365 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 23876 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 094 094 020 Old_age Always - 6861 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1097 188 Command_Timeout 0x0032 100 096 000 Old_age Always - 3759 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 051 036 045 Old_age Always In_the_past 49 (Min/Max 49/49 #998) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 20 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 78 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 578157 194 Temperature_Celsius 0x0022 049 064 000 Old_age Always - 49 (0 18 0 0 0) 195 Hardware_ECC_Recovered 0x001a 053 045 000 Old_age Always - 29958806 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 4 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 4 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 22868 (153 213 0) 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3790333358 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1937597633 254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 987 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 987 occurred at disk power-on lifetime: 23876 hours (994 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 cb a3 b6 09 Error: UNC at LBA = 0x09b6a3cb = 162964427 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 c8 a3 b6 49 00 05:50:04.649 READ FPDMA QUEUED 60 00 28 e0 a3 b6 49 00 05:50:04.617 READ FPDMA QUEUED 60 00 08 c0 a3 b6 49 00 05:50:04.515 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 05:50:04.513 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 05:50:04.512 IDENTIFY DEVICE Error 986 occurred at disk power-on lifetime: 23876 hours (994 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 cb a3 b6 09 Error: UNC at LBA = 0x09b6a3cb = 162964427 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 20 c0 a3 b6 49 00 05:50:02.009 READ FPDMA QUEUED 60 00 08 10 50 bb 49 00 05:50:01.961 READ FPDMA QUEUED ea 00 00 00 00 00 a0 00 05:49:55.547 FLUSH CACHE EXT 61 00 08 a0 33 4a 49 00 05:49:55.547 WRITE FPDMA QUEUED ea 00 00 00 00 00 a0 00 05:49:55.538 FLUSH CACHE EXT Error 985 occurred at disk power-on lifetime: 23874 hours (994 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 f6 00 08 0c Error: UNC at LBA = 0x0c0800f6 = 201851126 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 04:25:50.279 READ FPDMA QUEUED 60 00 08 f0 00 08 4c 00 04:25:50.257 READ FPDMA QUEUED 61 00 08 ff ff ff 4f 00 04:25:50.256 WRITE FPDMA QUEUED 60 00 08 90 f6 3c 4a 00 04:25:50.256 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 04:25:50.256 READ FPDMA QUEUED Error 984 occurred at disk power-on lifetime: 23874 hours (994 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 f6 00 08 0c Error: UNC at LBA = 0x0c0800f6 = 201851126 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 40 ff ff ff 4f 00 04:25:47.981 READ FPDMA QUEUED 60 00 80 28 9e 57 49 00 04:25:47.954 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 04:25:47.953 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 04:25:47.945 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 04:25:47.941 READ FPDMA QUEUED Error 983 occurred at disk power-on lifetime: 23874 hours (994 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 f6 00 08 0c Error: UNC at LBA = 0x0c0800f6 = 201851126 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 ff ff ff 4f 00 04:25:42.214 READ FPDMA QUEUED 60 00 d8 00 04 08 4c 00 04:25:42.209 READ FPDMA QUEUED 60 00 00 00 00 08 4c 00 04:25:42.207 READ FPDMA QUEUED 60 00 00 00 f6 07 4c 00 04:25:42.207 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 04:25:42.163 READ FPDMA QUEUED SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 0 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. | The drive has UNCorrectable sector errors, i.e. bad blocks. I doubt disabling NCQ or updating the BIOS helps against this. Interesting SMART attributes : Code: Select allID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 088 088 036 Pre-fail Always - 246 190 Airflow_Temperature_Cel 0x0022 051 036 045 Old_age Always In_the_past 49 (Min/Max 49/49 #998) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 4 The drive has currently 4 known unreadable sectors. 246 sectors were internally reallocated because they were defective. A defective sector cannot be reallocated until it is read successfully or overwritten with new data. The drive is quite hot and has suffered from over-heating at least once. This may explain the bad blocks. The kernel logs and SMART error logs show that sectors at LBA 162964427 and 201851126 were recently (not one year ago) found unreadable. According to the partition table, the former belongs to the root partition sda5 and the latter belongs to the home partition sda7. e2fsck detects and marks bad blocks only when run with the -c option. |
This works: Code: Select allsudo scanimage -L This doesn't: Code: Select allscanimage -L So only root user can scan images. libpam-systemd is installed. /etc/groups has: Code: Select allgrep sane /etc/group scanner:x:119:saned,myuser saned:x:120:myuser This wiki page: https://wiki.debian.org/Scanner#Permissions says: There is an appropriate vendor *.rules file in /etc/udev/rules.d or /lib/udev/rules.d. Never was able to figure out what it means. Any idea? Ran: Code: Select allsystemctl enable saned.socket sudo reboot Then have: Code: Select allsudo systemctl status saned.socket sudo: unable to resolve host aario-debian-pc: Name or service not known ● saned.socket - saned incoming socket Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: enabled) Active: active (listening) since Thu 2019-04-18 08:57:14 CEST; 21min ago Listen: [::]:6566 (Stream) Accepted: 0; Connected: 0; Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/saned.socket Apr 18 08:57:14 aario-debian-pc systemd[1]: Listening on saned incoming socket. saned cannot be enabled: Code: Select allsudo systemctl enable saned Synchronizing state of saned.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable saned Failed to enable unit: Unit file /lib/systemd/system/saned.service is masked. manually created the service file as in: https://help.ubuntu.com/community/SaneDaemonTutorial inside: Code: Select all/etc/systemd/system/saned@.service Wrote and saved: Code: Select all[Unit] Description=Scanner Service Requires=saned.socket [Service] ExecStart=/usr/sbin/saned User=saned Group=saned StandardInput=null StandardOutput=syslog StandardError=syslog # Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255 Then: Code: Select allsudo systemctl start saned.service sudo systemctl status saned.service sudo: unable to resolve host aario-debian-pc: Name or service not known ● saned.service - Scanner Service Loaded: loaded (/etc/systemd/system/saned.service; static; vendor preset: enabled) Active: inactive (dead) Apr 18 09:11:11 aario-debian-pc systemd[1]: Started Scanner Service. Apr 18 09:11:11 aario-debian-pc saned[20314]: saned (AF-indep+IPv6) from sane-backends 1.0.27 starting up Apr 18 09:11:11 aario-debian-pc saned[20314]: check_host: access by remote host: localhost Apr 18 09:11:11 aario-debian-pc saned[20314]: check_host: getaddrinfo for local hostname failed: Name or service not known Apr 18 09:11:11 aario-debian-pc saned[20314]: init: access by host localhost denied Apr 18 09:11:11 aario-debian-pc saned[20314]: saned exiting Apr 18 09:11:11 aario-debian-pc systemd[1]: saned.service: Succeeded. I'm out of ideas. Any other idea is highly appreciated. Thanks in advance. | aario wrote: Code: Select allsudo systemctl status saned.socket sudo: unable to resolve host aario-debian-pc: Name or service not known Code: Select allApr 18 09:11:11 aario-debian-pc saned[20314]: check_host: access by remote host: localhost Apr 18 09:11:11 aario-debian-pc saned[20314]: check_host: getaddrinfo for local hostname failed: Name or service not known Apr 18 09:11:11 aario-debian-pc saned[20314]: init: access by host localhost denied Could you post the contents of /etc/hostname (presumably "aario-debian-pc") and /etc/hosts? You have a weird configuration, where "localhost" is considered remote and your hostname is not even resolvable. You should at least have this in /etc/hosts: Code: Select all127.0.0.1 localhost 127.0.1.1 aario-debian-pc Not sure whether that addresses or solves your scanner problem, but it certainly won't hurt. |
I dist-upgrade last night on a jessie system. This morning I can't boot into the system the following message keep cycling on the screen: "Welcome to emergency mode! After logging in, type "journalctl -x" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode." I can't get to a tty, ctrl+alt+f1 does not yield anything. Any ideas? | Did you try any of the suggested actions? |
I don't understand my interface namings, which are named like so, enp* eth* rename* ? Seems like a big messy mix of naming standards. enp2s0f0 + enp2s0f1 is an PCI card eth0 + eth1 is an onboard controller rename4+rename5 is an PCI card snippet from: Code: Select alllrwxrwxrwx 1 root root 0 Apr 22 19:58 enp2s0f0 -> ../../devices/pci0000:00/0000:00:01.1/0000:02:00.0/net/enp2s0f0 lrwxrwxrwx 1 root root 0 Apr 22 19:58 enp2s0f1 -> ../../devices/pci0000:00/0000:00:01.1/0000:02:00.1/net/enp2s0f1 lrwxrwxrwx 1 root root 0 Apr 22 19:58 eth0 -> ../../devices/pci0000:00/0000:00:1d.0/0000:04:00.0/net/eth0 lrwxrwxrwx 1 root root 0 Apr 22 19:58 eth1 -> ../../devices/pci0000:00/0000:00:1d.1/0000:05:00.0/net/eth1 lrwxrwxrwx 1 root root 0 Apr 22 19:58 rename4 -> ../../devices/pci0000:00/0000:00:1c.0/0000:03:00.0/net/rename4 lrwxrwxrwx 1 root root 0 Apr 22 19:58 rename5 -> ../../devices/pci0000:00/0000:00:1c.0/0000:03:00.1/net/rename5 From /usr/share/doc/udev/README.Debian.gz I can see the following, that I should just rename the udev config, and reboot, which I did Code: Select allll /etc/udev/rules.d/ total 4 -rw-r--r-- 1 root root 1267 Apr 17 15:16 70-persistent-net.rules.old I can see in the message log, that the interfaces, are renamed, but I don't get why? Code: Select allgrep rename /var/log/messages Apr 22 19:59:11 myserver kernel: [ 2.318203] bnx2 0000:02:00.0 enp2s0f0: renamed from eth0 Apr 22 19:59:11 myserver kernel: [ 2.389831] bnx2 0000:02:00.1 enp2s0f1: renamed from eth1 Apr 22 19:59:11 myserver kernel: [ 2.413525] bnx2 0000:03:00.0 rename4: renamed from eth2 Apr 22 19:59:11 myserver kernel: [ 2.469517] bnx2 0000:03:00.1 rename5: renamed from eth3 Apr 22 19:59:11 myserver kernel: [ 2.497953] igb 0000:04:00.0 rename6: renamed from eth4 Apr 22 19:59:11 myserver kernel: [ 2.521745] igb 0000:05:00.0 eth1: renamed from eth0 Apr 22 19:59:11 myserver kernel: [ 2.572069] igb 0000:04:00.0 eth0: renamed from rename6 | lbm wrote:enp2s0f0 + enp2s0f1 is an PCI card It is the new "predictable" naming scheme. Note that unfortunately, "predictable" does not imply "persistent". enp2s0f0 designates an EtherNet interface on PCI bus #2, Slot #0, Function #0 (a PCI device may have multiple sub-devices called functions). ethN is the original kernel naming scheme. When predictable names are enabled, ethN names can only be set with udev rules. renameN is a transient name assigned by udev when ethX must be renamed as ethY but ethY already exists, so it must be renamed first. An example of how it is supposed to work is rename6. Such name should not remain after the renaming is done. This could indicate conflicting udev or systemd rules. By default all interfaces should be assigned predictable names. |
hi, i miss groupadd command in debian testing with 4.19.0.5 kernel (installed upgrading debian 9.8 live version ) Code: Select allroot@debiantesting:/# groupadd --help bash: groupadd : commande introuvable is this a lack due to previous live installation? or is this caused by testing version? how can i correct? seems it depends passwd package, it this a right way to reinstall passwd? thx | What makes you think it is missing, ? please use code boxes, and also show how you got root access. Code: Select allgarry@debian:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux buster/sid Release: testing Codename: buster garry@debian:~$ man groupadd ==== Seems like that manual is here === GROUPADD(8) System Management Commands GROUPADD(8) NAME groupadd - create a new group SYNOPSIS groupadd [options] group DESCRIPTION The groupadd command creates a new group account using the values specified on the command line plus the default values from the system. The new group will be entered into the system files as needed.===snip== ========= Now here is where you need to pay attention: If you did this: Code: Select allgarry@debian:~$ su Password: root@debian:/home/garry# groupadd --help bash: groupadd: command not found root@debian:/home/garry# It will not work, because you are not using the proper 'su' command: You should be using : Code: Select allgarry@debian:~$ su - Password: It works, the command is there, just like it should be. And I also do have the --help option. Code: Select all root@debian:~# groupadd --help Usage: groupadd [options] GROUP Options: -f, --force exit successfully if the group already exists, and cancel -g if the GID is already used -g, --gid GID use GID for the new group -h, --help display this help message and exit -K, --key KEY=VALUE override /etc/login.defs defaults -o, --non-unique allow to create groups with duplicate (non-unique) GID -p, --password PASSWORD use this encrypted password for the new group -r, --system create a system account -R, --root CHROOT_DIR directory to chroot into root@debian:~# ===== edit ==== This thread / topic goes into more details: su on buster, is this normal now? I think there are actually some other threads as well, maybe someone needs to make a "How to" tutorial, explaining how to use 'su' on Debian 10 Buster, but I imagine it would just be a waste of time, nobody searches or reads anything before posting anyway, just saying. Any way, no big deal, I do expect we are going to start getting a lot of this kind of question, and more when Buster is actually released. ============== edited ===== If you used sudo, the command should be there, and produce the same output" Code: Select allgarry@debian:~$ sudo groupadd --help [sudo] password for garry: Usage: groupadd [options] GROUP Options: -f, --force exit successfully if the group already exists, and cancel -g if the GID is already used -g, --gid GID use GID for the new group -h, --help display this help message and exit -K, --key KEY=VALUE override /etc/login.defs defaults -o, --non-unique allow to create groups with duplicate (non-unique) GID -p, --password PASSWORD use this encrypted password for the new group -r, --system create a system account -R, --root CHROOT_DIR directory to chroot into garry@debian:~$ |
Somebody may be able to finesse this config ... I had previously run a git daemon under inetd(8) and was just about to do so under stretch when I decided not to be a Luddite and use systemd . Various suggestions seemed to want to start it a permanent daemon. I really didn't want to do this as the only git interactions on this box would be push/pull , probably less than once a month. Also an interesting experience in using systemd. So if that's what you're trying to do, read on: /etc/systemd/system/git.socket: Code: Select allFile Edit Options Buffers Tools Help # /etc/systemd/system/git.socket: # GPV 08apr2019 Made this up , see my README in config # # Systemd is much more convoluted than simply using inetd(8). Doing this in /etc/inetd.conf is just one line: # # git stream tcp nowait user_git /usr/bin/git git daemon --inetd --verbose --enable=receive-pack --export-all /git # # With systemd, assuming we want the git daemon to startup when a request arrives, then go away (good for infrequent use), we need two fi\ les # # /etc/systemd/system/git.socket: (this file) # /etc/systemd/system/git@.service (note the @ sign, required) # # My understanding of what is happening here: # We have to HARDCODE 9418 [as always, bad programming practice] because it does not read /etc/services. This causes systemd to listen(\ 2) on TCP 9418 # We use Accept=yes, to cause systemd to issue the accept(2) # For each connection accept(2)ed systemd forks of a child to run what is given in /etc/systemd/system/git@.service (you'll note there'\ s no mention of that here) # The forked off child MUST NOT attempt to listen(2) on 9418. For git-daemon(1) (and many other daemons) this means the --inetd option # the child processes are "named" git@0.service,git@1.service ...git@99.service etc # [Unit] Description=GIT Socket # Pity we can't use /etc/services (how do we say TCP?) [Socket] ListenStream=9418 Accept=yes [Install] WantedBy=sockets.target /etc/systemd/system/git@.service: Code: Select all# /etc/systemd/system/git@.service: # GPV 08apr2019 Made this up , see my README in config # # Systemd is much more convoluted than simply using inetd(8). Doing this in /etc/inetd.conf is just one line: # # git stream tcp nowait user_git /usr/bin/git git daemon --inetd --verbose --enable=receive-pack --export-all /git # # You need to understand two files to make sense of this: # # /etc/systemd/system/git.socket: # /etc/systemd/system/git@.service (this file, note the @ sign, required) # In here we have: StandardInput=socket ... which means it's an inetd(8) style daemon (gets it's input from # stdin). Actually normally git-daemon(1) normally listen(2)s on port "git" (aka 9418/tcp, see /etc/services) and # does it's own accept(2). To stop it doing this we use the --inetd option # The other systemd "noise" is "Requires=git.socket" which causes systemd(1) to do the listen(2) before we start # This seems to break good information hiding principles. This "service" "knows" that it's connection arives via # "git.socket". It would be better if the relationship were the other way around. Then connections could arrive via # "TCP Socket", "Unix Doamin Socket", "A.N.Other mechanism" the daemon just sees STDIN. [Unit] Description=GIT as on-demand Service Requires=git.socket [Service] Type=simple ExecStart=/usr/lib/git-core/git-daemon --reuseaddr --enable=receive-pack --export-all --inetd --verbose --base-path=/git /git StandardInput=socket StandardError=journal TimeoutStopSec=5 #RuntimeMaxSec=10 [Install] WantedBy=multi-user.target | OK, So a change was needed systemctl was reporting "degraded" services, details being: Code: Select all# systemctl --state=failed UNIT LOAD ACTIVE SUB DESCRIPTION ● session-c1.scope loaded failed failed Session c1 of user graeme ● git.service not-found failed failed git.service ● git@0-10.11.12.13:9418-10.11.12.105:33854.service loaded failed failed GIT as on-demand Service ● git@0.service loaded failed failed GIT as on-demand Service ● git@1-10.11.12.13:9418-10.11.12.105:33890.service loaded failed failed GIT as on-demand Service ● git@2-10.11.12.13:9418-10.11.12.105:33896.service loaded failed failed GIT as on-demand Service ● git@3-10.11.12.13:9418-10.11.12.105:33898.service loaded failed failed GIT as on-demand Service ● git@4-10.11.12.13:9418-10.11.12.105:33908.service loaded failed failed GIT as on-demand Service ● git@5-10.11.12.13:9418-10.11.12.105:50692.service loaded failed failed GIT as on-demand Service So changed it to a oneshot service (meaning systemd does not expect it to stick around) Code: Select all# git diff 0462082453fb5f12d24b562038ece294b4281dc4 -- etc/systemd/system/git@.service WARNING: terminal is not fully functional - (press RETURN) diff --git a/etc/systemd/system/git@.service b/etc/systemd/system/git@.service index 0a7a233..c4a447f 100644 --- a/etc/systemd/system/git@.service +++ b/etc/systemd/system/git@.service @@ -1,5 +1,6 @@ # /etc/systemd/system/git@.service: # GPV 08apr2019 Made this up , see my README in config +# GPV 26may2019 changed to type=oneshot (from simple) as this does not remain running longterm # # Systemd is much more convoluted than simply using inetd(8). Doing this in /etc/inetd.conf is just one line: # @@ -25,7 +26,7 @@ Description=GIT as on-demand Service Requires=git.socket [Service] -Type=simple +Type=oneshot ExecStart=/usr/lib/git-core/git-daemon --reuseaddr --enable=receive-pack --export-all --inetd --verbose --base-path=/git /git StandardInput=socket StandardError=journal Now it's no longer reported as degraded: Code: Select all# systemctl status ● zbox State: running Jobs: 0 queued Failed: 0 units Since: Thu 2019-03-21 12:34:05 GMT; 2 months 5 days ago ABTW, I did a Code: Select all# systemctl reset-failed to clear out the old failed services. |
I am running kde with Debian version 9.9.0 My laptop was connecting to wifi at home so I know I have installed the correct driver (firmware-iwlwifi) Now I am trying to connect to another network, one that I know is on (other people around me getting on) After clicking on the network icon in the kde panel, I see the network. Clicking connect brings up a dialog: Password dialog - KDE Daemon For accessing the wireless network 'gamma' you need to provide a password below I enter the wireless password for the router, click OK, And then I get the exact same dialogue back again. This just repeats. Once I finally give up I briefly see a message "No secrets were provided" Does anyone know a solution to this. My laptop does not have an ethernet port. | Very sorry. In transposing the password characters were reordered. |
Hello, I'm trying to run Deluge Web using Debian Stable, i've installed Deluge from the package manager: Code: Select allapt install deluged deluge-web deluge-webui Deluged has a systemd daemon that runs fine and Debian create a user called debian-deluged with home in /var/lib/deluged. And this user is used by deluged daemon (checked with ps by checking the PID). But debian-web and debian-webui won't install any service on my machine, so i've followed Deluge Web UI (deluge-web) Service from the guide changing the username from deluge to debian-deluged to match deluged username. When i open the web interface i get only that the daemon is not running. Obviously no error showing there, but searching in the log files from the server: /var/log/deluged/daemon.log Code: Select all[INFO ] 01:58:28 configmanager:70 Setting config directory to: /var/lib/deluged/config [INFO ] 01:58:28 daemon:127 Deluge daemon 1.3.13 [INFO ] 01:58:28 configmanager:70 Setting config directory to: /var/lib/deluged/config [INFO ] 01:58:28 core:87 Starting libtorrent 1.1.1.0 session.. [INFO ] 01:58:28 rpcserver:369 Starting DelugeRPC server localhost:58846 [WARNING ] 01:58:28 preferencesmanager:507 GeoIP Unavailable [INFO ] 01:58:28 torrentmanager:650 Successfully loaded state file: /var/lib/deluged/config/state/torrents.state [INFO ] 01:58:35 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58626 [ERROR ] 01:58:35 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:35 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:37 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58628 [ERROR ] 01:58:37 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:37 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:39 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58630 [INFO ] 01:58:39 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58632 [ERROR ] 01:58:39 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [ERROR ] 01:58:39 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:39 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:39 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:41 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58634 [ERROR ] 01:58:41 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:41 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:43 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58636 [ERROR ] 01:58:43 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:43 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:45 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58638 [ERROR ] 01:58:45 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:45 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:47 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58640 [ERROR ] 01:58:47 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:47 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:49 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58642 [ERROR ] 01:58:49 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:49 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:51 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58644 [ERROR ] 01:58:51 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:51 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:53 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58646 [ERROR ] 01:58:53 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:53 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:55 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58648 [ERROR ] 01:58:55 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:55 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:57 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58650 [ERROR ] 01:58:57 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:57 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:58:59 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58652 [ERROR ] 01:58:59 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:58:59 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:01 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58654 [ERROR ] 01:59:01 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:01 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:04 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58656 [ERROR ] 01:59:04 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:04 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:05 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58658 [ERROR ] 01:59:06 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:06 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:08 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58660 [ERROR ] 01:59:08 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:08 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:10 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58662 [ERROR ] 01:59:10 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:10 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:13 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58664 [ERROR ] 01:59:13 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:13 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:14 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58666 [ERROR ] 01:59:15 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:15 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:17 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58668 [ERROR ] 01:59:17 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:17 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:19 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58670 [ERROR ] 01:59:19 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:19 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:21 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58672 [ERROR ] 01:59:21 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:21 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:23 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58674 [ERROR ] 01:59:23 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:23 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:25 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58676 [ERROR ] 01:59:25 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:25 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:27 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58678 [ERROR ] 01:59:27 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:27 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:29 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58680 [ERROR ] 01:59:29 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:29 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:31 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58682 [ERROR ] 01:59:31 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:31 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:33 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58684 [ERROR ] 01:59:33 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:33 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:35 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58686 [ERROR ] 01:59:35 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:35 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:37 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58688 [ERROR ] 01:59:37 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:37 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:40 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58690 [ERROR ] 01:59:40 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:40 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:42 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58692 [ERROR ] 01:59:42 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:42 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:44 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58694 [ERROR ] 01:59:44 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:44 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:46 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58696 [ERROR ] 01:59:46 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:46 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. [INFO ] 01:59:48 rpcserver:206 Deluge Client connection made from: 127.0.0.1:58698 [ERROR ] 01:59:48 rpcserver:268 Username does not exist Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch ret = component.get("AuthManager").authorize(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize raise BadLoginError("Username does not exist") BadLoginError: Username does not exist [INFO ] 01:59:48 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. journalctl -u deluged Code: Select all-- Logs begin at Mon 2019-04-15 22:34:35 -03, end at Tue 2019-04-16 02:55:34 -03. -- Apr 16 01:43:58 windhelm systemd[1]: Starting LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:43:58 windhelm deluged[8197]: Starting Deluge BitTorrent Daemon: deluged Not starting Deluge BitTorrent Daemon deluged, disabled in /etc/default/deluged. Apr 16 01:43:58 windhelm systemd[1]: Started LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:45:33 windhelm systemd[1]: Stopping LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:45:33 windhelm deluged[8358]: Stopping Deluge BitTorrent Daemon: deluged. Apr 16 01:45:33 windhelm systemd[1]: Stopped LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:45:33 windhelm systemd[1]: Starting LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:45:33 windhelm deluged[8365]: Starting Deluge BitTorrent Daemon: deluged. Apr 16 01:45:33 windhelm systemd[1]: Started LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:46:12 windhelm systemd[1]: Stopping LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:46:12 windhelm deluged[8451]: Stopping Deluge BitTorrent Daemon: deluged. Apr 16 01:46:12 windhelm systemd[1]: Stopped LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:46:12 windhelm systemd[1]: Starting LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:46:12 windhelm deluged[8457]: Starting Deluge BitTorrent Daemon: deluged. Apr 16 01:46:12 windhelm systemd[1]: Started LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:52:37 windhelm systemd[1]: Stopping LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:52:37 windhelm deluged[8707]: Stopping Deluge BitTorrent Daemon: deluged. Apr 16 01:52:37 windhelm systemd[1]: Stopped LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:52:37 windhelm systemd[1]: Starting LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:52:37 windhelm deluged[8716]: Starting Deluge BitTorrent Daemon: deluged. Apr 16 01:52:37 windhelm systemd[1]: Started LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:54:41 windhelm systemd[1]: Stopping LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:54:41 windhelm deluged[8778]: Stopping Deluge BitTorrent Daemon: deluged. Apr 16 01:54:41 windhelm systemd[1]: Stopped LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:54:41 windhelm systemd[1]: Starting LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:54:41 windhelm deluged[8787]: Starting Deluge BitTorrent Daemon: deluged. Apr 16 01:54:41 windhelm systemd[1]: Started LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:58:28 windhelm systemd[1]: Stopping LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:58:28 windhelm deluged[8863]: Stopping Deluge BitTorrent Daemon: deluged. Apr 16 01:58:28 windhelm systemd[1]: Stopped LSB: Start or stop the Deluge BitTorrent daemon.. Apr 16 01:58:28 windhelm systemd[1]: Starting LSB: Start or stop the Deluge BitTorrent daemon.... Apr 16 01:58:28 windhelm deluged[8871]: Starting Deluge BitTorrent Daemon: deluged. Apr 16 01:58:28 windhelm systemd[1]: Started LSB: Start or stop the Deluge BitTorrent daemon.. journalctl -u deluge-web Code: Select all-- Logs begin at Mon 2019-04-15 22:34:35 -03, end at Tue 2019-04-16 02:55:58 -03. -- Apr 16 01:49:04 windhelm systemd[1]: Starting Deluge Bittorrent Client Web Interface... Apr 16 01:49:09 windhelm systemd[1]: Started Deluge Bittorrent Client Web Interface. Apr 16 01:49:39 windhelm deluge-web[8580]: [ERROR ] 01:49:39 client:391 RPCError Message Received! Apr 16 01:49:39 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:39 windhelm deluge-web[8580]: RPCRequest: daemon.login(, ) Apr 16 01:49:39 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:39 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch Apr 16 01:49:39 windhelm deluge-web[8580]: ret = component.get("AuthManager").authorize(*args, **kwargs) Apr 16 01:49:39 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize Apr 16 01:49:39 windhelm deluge-web[8580]: raise BadLoginError("Username does not exist") Apr 16 01:49:39 windhelm deluge-web[8580]: BadLoginError: Username does not exist Apr 16 01:49:39 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:39 windhelm deluge-web[8580]: [ERROR ] 01:49:39 client:391 RPCError Message Received! Apr 16 01:49:39 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:39 windhelm deluge-web[8580]: RPCRequest: daemon.login(, ) Apr 16 01:49:39 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:39 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch Apr 16 01:49:39 windhelm deluge-web[8580]: ret = component.get("AuthManager").authorize(*args, **kwargs) Apr 16 01:49:39 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize Apr 16 01:49:39 windhelm deluge-web[8580]: raise BadLoginError("Username does not exist") Apr 16 01:49:39 windhelm deluge-web[8580]: BadLoginError: Username does not exist Apr 16 01:49:39 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:41 windhelm deluge-web[8580]: /usr/lib/python2.7/dist-packages/deluge/_libtorrent.py:59: RuntimeWarning: to-Python converter for boost::shared_ptr<libtorrent::alert> already registered; second conversion method ignored. Apr 16 01:49:41 windhelm deluge-web[8580]: import libtorrent as lt Apr 16 01:49:41 windhelm deluge-web[8580]: [ERROR ] 01:49:41 client:391 RPCError Message Received! Apr 16 01:49:41 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:41 windhelm deluge-web[8580]: RPCRequest: daemon.login(, ) Apr 16 01:49:41 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:41 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch Apr 16 01:49:41 windhelm deluge-web[8580]: ret = component.get("AuthManager").authorize(*args, **kwargs) Apr 16 01:49:41 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize Apr 16 01:49:41 windhelm deluge-web[8580]: raise BadLoginError("Username does not exist") Apr 16 01:49:41 windhelm deluge-web[8580]: BadLoginError: Username does not exist Apr 16 01:49:41 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:41 windhelm deluge-web[8580]: [ERROR ] 01:49:41 rpcserver:378 Couldn't listen on localhost:58846: [Errno 98] Address already in use. Apr 16 01:49:43 windhelm deluge-web[8580]: [ERROR ] 01:49:43 client:391 RPCError Message Received! Apr 16 01:49:43 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:43 windhelm deluge-web[8580]: RPCRequest: daemon.login(, ) Apr 16 01:49:43 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:43 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch Apr 16 01:49:43 windhelm deluge-web[8580]: ret = component.get("AuthManager").authorize(*args, **kwargs) Apr 16 01:49:43 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize Apr 16 01:49:43 windhelm deluge-web[8580]: raise BadLoginError("Username does not exist") Apr 16 01:49:43 windhelm deluge-web[8580]: BadLoginError: Username does not exist Apr 16 01:49:43 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:45 windhelm deluge-web[8580]: [ERROR ] 01:49:45 client:391 RPCError Message Received! Apr 16 01:49:45 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:45 windhelm deluge-web[8580]: RPCRequest: daemon.login(, ) Apr 16 01:49:45 windhelm deluge-web[8580]: -------------------------------------------------------------------------------- Apr 16 01:49:45 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 262, in dispatch Apr 16 01:49:45 windhelm deluge-web[8580]: ret = component.get("AuthManager").authorize(*args, **kwargs) Apr 16 01:49:45 windhelm deluge-web[8580]: File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 89, in authorize Clearly the error is BadLoginError("Username does not exist") Upon searching on the web i found that i need to create an auth file, since both deluged and deluge-web share the same user, i've created the inexistent file /var/lib/deluged/.config/deluge/auth and added: Code: Select alldebian-deluged:deluge:10 with the owner beign debian-deluged:debian-deluged and since /var/lib/deluged is the home for debian-deluged as its in /etc/passwd. But it didn't work. The directory /var/lib/deluged/.config/deluge existed, telling me that deluge-web was working but there was no auth file on it. Then, i've added the same line to the /var/lib/deluged/config/auth wich i suppose was the deluged auth file. This file had the Code: Select alllocalclient:cc9c32efd5440f6ea5224a196432d6f97e5212f1:10 i just added below. Also didn't work. My setup is Debian GNU/Linux 9 with Linux 4.9.0-8-amd64 My deluge is 1.3.13 / libtorrent: 1.1.1.0 All installed and updated by debian repo | Solved the problem by creating another user and editing both deluge-web.service that i've created and /etc/init.d/deluged to use deluge user instead of debian-deluged pointed to /var/lib/deluge Don't know if it's because of the minus signal or the username size, but deluge doesn't like the username debian-deluged. I filled a bug report for the packager of deluged to change the username for the default deluge as from Deluge documentation since Debian doesn't use the latest release of deluged i cannot fill a bug report on deluge. Until its solved, you can just create a deluge system user: Code: Select allgroupadd deluge useradd -r -d /var/lib/deluge -g deluge deluge mkdir -p /var/lib/deluge chown -R deluge:deluge /var/lib/deluge and edit both /etc/init.d/deluged and your own /etc/systemd/system/deluge-web.service to use this user, then deluge will just work fine. |
i am trying to access the site https://neuvoo.com/ (ip address - 192.99.4.68) on my imac debian install on chrome i get Code: Select allThis site can’t be reached neuvoo.com’s server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN on firefox Code: Select allHmm. We’re having trouble finding that site. We can’t connect to the server at www.neuvoo.com. If that address is correct, here are three other things you can try: Try again later. Check your network connection. If you are connected but behind a firewall, check that Firefox has permission to access the Web. the site is up also i can access the site on windows on my laptop which is connected to the same network via wifi through a repeater i am able to do a traceroute using the ip address Code: Select all# traceroute 192.99.4.68 traceroute to 192.99.4.68 (192.99.4.68), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 0.481 ms 0.486 ms 0.514 ms 2 102.132.136.1 (102.132.136.1) 2.725 ms 3.538 ms 3.675 ms 3 154.0.3.97 (154.0.3.97) 4.685 ms * * 4 154.0.5.1 (154.0.5.1) 2.212 ms 2.207 ms 2.144 ms 5 u136-cust.coolideas.co.za (154.0.5.130) 2.345 ms 2.354 ms 2.354 ms 6 154.0.5.99 (154.0.5.99) 2.672 ms 1.746 ms 1.718 ms 7 154.0.4.250 (154.0.4.250) 158.813 ms 154.0.4.254 (154.0.4.254) 158.810 ms 154.0.4.250 (154.0.4.250) 158.722 ms 8 154.0.5.18 (154.0.5.18) 158.864 ms 158.820 ms 158.843 ms 9 * * * 10 be100-1298.nwk-5-a9.nj.us (192.99.146.133) 227.646 ms 227.652 ms 227.827 ms 11 be100-1323.bhs-g2-nc5.qc.ca (192.99.146.138) 238.458 ms 238.417 ms 238.359 ms 12 * * * 13 be50-7.bhs-3a-a9.qc.ca (198.27.73.94) 257.504 ms be50-7.bhs-3b-a9.qc.ca (198.27.73.98) 372.763 ms 371.519 ms 14 ns515532.ip-192-99-4.net (192.99.4.68) 253.248 ms 237.429 ms 236.738 ms cat /etc/resolv.conf Code: Select all# Generated by NetworkManager search 192.168.1.1 nameserver 192.168.1.1 when i manually edit /etc/resolv.conf with Code: Select allecho "nameserver 8.8.8.8" > /etc/resolv.conf i am then able to access the site what could be happening? | It is interesting to note that neuvoo.com resolves to not less than 27 IP addresses, which is rather uncommon. Code: Select allhost neuvoo.com ;; Truncated, retrying in TCP mode. neuvoo.com has address 54.39.186.68 neuvoo.com has address 198.27.69.35 neuvoo.com has address 142.44.244.152 neuvoo.com has address 192.99.6.114 neuvoo.com has address 54.39.59.114 neuvoo.com has address 54.39.57.36 neuvoo.com has address 54.39.57.40 neuvoo.com has address 54.39.187.238 neuvoo.com has address 192.99.0.219 neuvoo.com has address 54.39.59.115 neuvoo.com has address 192.99.0.221 neuvoo.com has address 142.44.164.24 neuvoo.com has address 54.39.180.68 neuvoo.com has address 54.39.189.62 neuvoo.com has address 192.99.6.69 neuvoo.com has address 54.39.56.120 neuvoo.com has address 54.39.57.37 neuvoo.com has address 54.39.57.41 neuvoo.com has address 192.99.4.68 neuvoo.com has address 54.39.184.164 neuvoo.com has address 142.44.164.222 neuvoo.com has address 54.39.59.121 neuvoo.com has address 54.39.57.5 neuvoo.com has address 54.39.59.118 neuvoo.com has address 192.99.6.56 neuvoo.com has address 142.44.164.236 neuvoo.com has address 142.44.164.230 This makes the DNS reply quite larger than average, and exceeds the maximum DNS payload size over UDP transport defined in the original DNS specifcation (512 bytes) which cause a truncated reply to be sent. There are two methods to extend the DNS payload size : - use TCP transport instead of UDP, like the "host" command did above ; - use EDNS extension, which allows payload up to 4096 bytes over UDP, like the "dig" command does by default : Code: Select alldig neuvoo.com ; <<>> DiG 9.9.5-9+deb8u17-Debian <<>> neuvoo.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63095 ;; flags: qr rd ra; QUERY: 1, ANSWER: 27, AUTHORITY: 4, ADDITIONAL: 9 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;neuvoo.com. IN A ;; ANSWER SECTION: neuvoo.com. 60 IN A 192.99.6.114 neuvoo.com. 60 IN A 54.39.180.68 neuvoo.com. 60 IN A 142.44.164.222 etc. I suspect that the glibc resolver and Windows use different methods, and the DNS relay/proxy server embedded in the router does not handle correctly the method used by the glibc resolver. Comparing the outcome of the following commands may confirm or not : Code: Select alldig neuvoo.com +edns dig neuvoo.com +noedns |
Hi, i installed Debian 8.2 x64 on Hyper-V Server. Debian gets IP settings from Windows DHCP. DHCP configuration is below: with default settings of /etc/dhcp/dhclient.conf Debian doesn't get default gateway: Code: Select allroot@host:/etc/network# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.255.9.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 172.65.0.0 10.255.9.1 255.255.255.0 UG 0 0 0 eth0 as a result: there is no internet access. In /etc/dhcp/dhclient.conf i commented some line about 121 option, and deleted it from "request": Code: Select allroot@host:~# cat /etc/dhcp/dhclient.conf # Configuration file for /sbin/dhclient, which is included in Debian's #option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, dhcp6.name-servers, dhcp6.domain-search, netbios-name-servers, netbios-scope, interface-mtu, ntp-servers; and then Debian gets default gateway and internet works: Code: Select allroot@host:~# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.255.9.1 0.0.0.0 UG 0 0 0 eth0 10.255.9.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 how i can fix it, that default gateway and option 121 does not working together? Thank you! | update: in Debian 7.9 all works perfect! temporary solution by adding to /etc/network/interfaces Code: Select allup route add default gw 10.255.9.1 dev eth0 |
Hello, I've successfully managed to install the latest currently available Buster distro (frozen - 2019-03-11) on a ZFS root, booting in UEFI. This, in itself, already makes me rather happy Unfortunately, I'm still facing a problem that I so far was unable to resolve by myself, despite searching for hours, not to say days. This is the reason I'm finally posting here in hope that someone more enlightened than I am might help me find a solution... Here is the situation: On a UEFI system, Debian Buster (frozen-20190311) has been installed on a single NVMe drive, using two partitions, one for the ESP, the other one being dedicated for ZFS. The ZFS configuration / installation was mainly carried out following the GitHub's zfsonlinux HOWTO for Debian Stretch https://github.com/zfsonlinux/zfs/wiki/ ... oot-on-ZFS. Therefore, the configuration of the disk, its partitions, ZFS datasets and /etc/fstab file are as follow: Code: Select all$ blkid /dev/nvme0n1: LABEL="rpool" UUID="980046881818473778" UUID_SUB="11196991732143542666" TYPE="zfs_member" PTUUID="40008bd4-3d2a-4f78-8c32-2f48ad9873d4" PTTYPE="gpt" /dev/nvme0n1p1: LABEL="rpool" UUID="980046881818473778" UUID_SUB="11196991732143542666" TYPE="zfs_member" PARTUUID="845abebe-7785-4785-8382-3761982fbcd6" /dev/nvme0n1p3: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="8241-499B" TYPE="vfat" PARTUUID="581b4260-b5c1-4389-8e11-aa43f71d35b9" $ lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT nvme0n1 zfs_member rpool 980046881818473778 ├─nvme0n1p1 zfs_member rpool 980046881818473778 └─nvme0n1p3 vfat EFI 8241-499B 507.3M 1% /boot/efi $ zfs list -r -o name,mountpoint,canmount,exec,setuid rpool NAME MOUNTPOINT CANMOUNT EXEC SETUID rpool / off on on rpool/ROOT none off on on rpool/ROOT/debian-10 / noauto on on rpool/ROOT/debian-10/opt /opt on on on rpool/ROOT/debian-10/var /var off off off rpool/ROOT/debian-10/var/cache /var/cache on off off rpool/ROOT/debian-10/var/log legacy on off off rpool/ROOT/debian-10/var/tmp legacy on on off rpool/home /home on on off rpool/home/root /root on on off rpool/tmp legacy on on off $ cat /etc/fstab # EFI BOOT PARTITION PARTUUID=581b4260-b5c1-4389-8e11-aa43f71d35b9 /boot/efi vfat noatime,nofail,x-systemd.device-timeout=1 0 1 # ZFS FILESYSTEM LEGACY MOUNTS rpool/ROOT/debian-10/var/log /var/log zfs noatime,nodev,noexec,nosuid 0 0 rpool/ROOT/debian-10/var/tmp /var/tmp zfs noatime,nodev,nosuid 0 0 rpool/tmp /tmp zfs noatime,nodev,nosuid 0 0 Once the system installation was completed, time had come for the GRUB(2) installation, which was executed as follow: Code: Select all$ apt install --yes grub-efi-am64 $ grub-probe / zfs $ update-initramfs -u -k all $ update-grub $ grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=debian-10 --recheck --no-floppy ... No error reported $ ls /boot/grub/*/zfs.mod /boot/grub/x86_64-efi/zfs.mod At this point, the content of /boot becomes: Code: Select all$ ls -l /boot/ total 32823 -rw-r--r-- 1 root root 206411 Jan 17 19:56 config-4.19.0-2-amd64 drwxr-xr-x 3 root root 4096 Jan 1 1970 efi drwxr-xr-x 5 root root 9 Mar 18 09:59 grub -rw-r--r-- 1 root root 27223819 Mar 18 08:49 initrd.img-4.19.0-2-amd64 -rw-r--r-- 1 root root 3345492 Jan 17 19:56 System.map-4.19.0-2-amd64 -rw-r--r-- 1 root root 5180704 Jan 17 19:56 vmlinuz-4.19.0-2-amd64 ls -l /boot/efi/EFI/debian-10 total 3772 -rwxr-xr-x 1 root root 72144 Mar 18 09:27 fbx64.efi -rwxr-xr-x 1 root root 113 Mar 18 09:27 grub.cfg -rwxr-xr-x 1 root root 1435040 Mar 18 09:27 grubx64.efi -rwxr-xr-x 1 root root 1168464 Mar 18 09:27 mmx64.efi -rwxr-xr-x 1 root root 1169528 Mar 18 09:27 shimx64.efi $ ls -l /boot/grub/ total 1584 drwxr-xr-x 2 root root 3 Mar 15 12:40 fonts -r--r--r-- 1 root root 5675 Mar 18 10:14 grub.cfg -rw-r--r-- 1 root root 1024 Mar 15 12:40 grubenv drwxr-xr-x 2 root root 40 Mar 18 09:27 locale -rw-r--r-- 1 root root 2396122 Mar 15 12:40 unicode.pf2 drwxr-xr-x 2 root root 270 Mar 18 09:27 x86_64-efi The interesting part of /boot/grub/grub.cfg being: Code: Select all$ cat /boot/grub/grub.cfg ... menuentry 'Debian Buster GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-0d99d3724e04f532' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod zfs if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 0d99d3724e04f532 else search --no-floppy --fs-uuid --set=root 0d99d3724e04f532 fi echo 'Loading Linux 4.19.0-2-amd64 ...' linux /ROOT/debian-10@/boot/vmlinuz-4.19.0-2-amd64 root=ZFS=rpool/ROOT/debian-10 ro echo 'Loading initial ramdisk ...' initrd /ROOT/debian-10@/boot/initrd.img-4.19.0-2-amd64 } ... While the content of /boot/efi/EFI/debian-10/grub.cfg is: Code: Select allsearch.fs_uuid 0d99d3724e04f532 root set prefix=($root)'/ROOT/debian-10@/boot/grub' configfile $prefix/grub.cfg Unfortunately, as stated at the beginning of this post, trying to boot the system with this in place immediately brings up the grub command line (grub>). Which means grub was able to load but cannot locate the grub.cfg file... Nevertheless, it is then quite possible to boot the system by typing one of the following sequences at the grub> prompt: Code: Select allgrub> insmod part_gpt grub> search --set --label rpool grub> linux /ROOT/debian-10@/boot/vmlinuz-4.19.0-2-amd64 root=ZFS=rpool/ROOT/debian-10 ro grub> initrd /ROOT/debian-10@/boot/initrd.img-4.19.0-2-amd64 grub> boot Or: Code: Select allgrub> search --label --set root rpool grub> prefix=($root)'/ROOT/debian-10@/boot/grub' grub> configfile $prefix/grub.cfg This second one bringing us back to the Grub start menu that we'd so much like to reach immediately upon system startup ! I, obviously, tried to modify the /boot/efi/EFI/debian-10/grub.cfg file, inserting each of the above sequences, but to no avail I read somewhere that this file was not used during the efi boot process, and that it was hardcoded into the sibling grubx64.efi executable. Which I was unable to confirm, even using GHex trying to explore it... One thing I could determine, using efibootmgr, is that it is shimx64.efi that is called during the UEFI boot process: Code: Select all$ efibootmgr -v BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000 Boot0000* debian-10 HD(3,GPT,581b4260-b5c1-4389-8e11-aa43f71d35b9,0x800,0x100000)/File(\EFI\debian-10\shimx64.efi) One other thing I wasn't able to figure out is: where does the UUID used in both grub.cfg come from ? I've parsed all /dev/disk/by-id, zpool / zfs get guid and blkid output but couldn't determine where the 0d99d3724e04f532 value used in both /boot/grub/grub.cfg and /boot/efi/EFI/debian-10/grub.cfg came from ! Thus, here I am, at least able to use the system although forced to type those grub commands each time I start it up... And, since this is supposed to become my day to day laptop I'd really like to find a way to have grub immediately locating its config file, which I think must be achievable, specially since it is doable from the grub command line ! But, once again, I haven't been able to find a way to do it... until maybe one of you reading this brings me the so much expected solution ? Thank you. | tibdm wrote:I've parsed all /dev/disk/by-id, zpool / zfs get guid and blkid output but couldn't determine where the 0d99d3724e04f532 value used in both /boot/grub/grub.cfg and /boot/efi/EFI/debian-10/grub.cfg came from ! 0d99d3724e04f532 is the hexadecimal notation for decimal 980046881818473778. This is the first time I see a UUID with decimal notation. Edit : did you compare the value of $root and $prefix before and after executing the search command ? |
I have installed dunst notification manager but whenever I try to run it this is what I get Code: Select allName Lost. Is Another notification daemon running? But it is not. Code: Select all$ ps -elf | grep dunst 0 S zurg11 2796 2794 0 80 0 - 1182 pipe_w 17:55 pts/0 00:00:00 grep --color=auto dunst $ ps -elf | grep noti 0 S zurg11 2798 2794 0 80 0 - 1182 pipe_w 17:55 pts/0 00:00:00 grep --color=auto noti I have also download d-feet and searched for org.freedesktop.Notifications but nothing showed up. Dunst's FAQ also says I should check $DBUS_SESSION_BUS_ADDRESS, and it's true it is unset but I don't know how to set it. Please help. | Zurg11 wrote:But it is not. Did you try the gdbus command suggested in the FAQ? Find it in the libglib2.0-bin package. FWIW, I can run dunst with DBUS_SESSION_BUS_ADDRESS unset. |
I am not sure how this happened, but I can no longer see wireless networks in network manager. This was working last night but is no longer working now. I'm running a Dell XPS 9630. Code: Select all$ sudo dmidecode | grep "Product Name" Product Name: XPS 13 9360 Product Name: 02PG84 $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux buster/sid Release: unstable Codename: sid $ uname -r 4.19.0-4-amd64 I have the firmware atheros wifi package installed, as per https://wiki.debian.org/InstallingDebia ... PS_13_9360. Code: Select all$ apt list --installed | grep atheros WARNING: apt does not have a stable CLI interface. Use with caution in scripts. firmware-atheros/unstable,now 20190114-1 all [installed] I don't see my wifi interface in `ip addr` or in `lshw -C network`. Code: Select all$ ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:c0:a9:e7:ab brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 3: enx00e04c110116: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:e0:4c:11:01:16 brd ff:ff:ff:ff:ff:ff inet 10.13.14.142/16 brd 10.13.255.255 scope global dynamic noprefixroute enx00e04c110116 valid_lft 1692sec preferred_lft 1692sec inet6 fe80::2e0:4cff:fe11:116/64 scope link noprefixroute valid_lft forever preferred_lft forever $ sudo lshw -C network *-network:0 description: Ethernet interface physical id: 2 logical name: docker0 serial: 02:42:c0:a9:e7:ab capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=172.17.0.1 link=no multicast=yes *-network:1 description: Ethernet interface physical id: 3 bus info: usb@2:2.3 logical name: enx00e04c110116 serial: 00:e0:4c:11:01:16 size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.09.9 duplex=full ip=10.13.14.142 link=yes multicast=yes port=MII speed=1Gbit/s Lastly, I don't see my wireless device in `lspci`. Code: Select all$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 08) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d10] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point LPC Controller/eSPI Controller [8086:9d4e] (rev 21) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 01:00.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] [8086:1576] 02:00.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] [8086:1576] 02:01.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] [8086:1576] 02:02.0 PCI bridge [0604]: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] [8086:1576] 39:00.0 USB controller [0c03]: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge] [8086:15b5] 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 3c:00.0 Non-Volatile memory controller [0108]: SK hynix Device [1c5c:1527] I've tried restarting my laptop, hitting the Fn+PrtScr combo, and reinstalling the firmware-atheros package to no avail. Any help would be appreciated! | Looks like your wireless card might be either dead or disconnected. Load up a "live" ISO image (that includes the non-free firmware) to eliminate misconfiguration as a cause. |
This is a tough one for me to figure out... If I simply do apt-get update ; apt-get upgrade there are a couple of applications that were loaded before but are no longer needed - here is the output: Code: Select allroot@BigMutt:~# apt-get update ; apt-get upgrade Hit:1 http://security.debian.org stretch/updates InRelease Ign:2 http://deb.debian.org/debian stretch InRelease Hit:3 http://linux.teamviewer.com/deb stable InRelease Hit:4 http://download.virtualbox.org/virtualbox/debian stretch InRelease Ign:5 http://dl.google.com/linux/chrome/deb stable InRelease Hit:6 http://deb.debian.org/debian stretch-updates InRelease Hit:7 http://security.debian.org/debian-security stretch/updates InRelease Hit:8 http://dl.google.com/linux/chrome/deb stable Release Hit:9 http://deb.debian.org/debian stretch Release Hit:10 http://www.deb-multimedia.org stretch-backports InRelease Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: exim4-base exim4-config exim4-doc-html eximon4 libdate-manip-perl linux-image-4.9.0-6-amd64 swaks Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Somehow the basic "mail" application got deleted - don't know how - and, when I attempt to reinstall it, all hell breaks loose with huge numbers of packages/apps cited for removal (Real Scary) - here is the output: Code: Select allroot@BigMutt:~# apt-get install mailutils Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apper-data cups-pk-helper dc debconf-kde-data debconf-kde-helper ed:i386 exim4-base exim4-config exim4-doc-html eximon4 gir1.2-atspi-2.0 gir1.2-gnomekeyring-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-wnck-3.0 hplip-data libakonadi-kde4 libakonadi-kmime4 libakonadiprotocolinternals1 libart-2.0-2 libasr0:i386 libatk-adaptor libbrlapi0.6 libdate-manip-perl libdebconf-kde1 libevent-2.0-5:i386 libgnome-keyring-common libgnome-keyring0 libkidletime4 liblimba0 libmpdec2 libpython3-stdlib libpython3.5 libpython3.5-minimal libpython3.5-stdlib libqjson0 libqt4-help libqt4-scripttools libqt4-test libqtassistantclient4 libsane-hpaio libssl1.0.2:i386 libwnck-3-0 libwnck-3-common libxres1 linux-image-4.9.0-6-amd64 mscompress polkit-kde-1 python-apt-common python3-chardet python3-debian python3-httplib2 python3-louis python3-pexpect python3-pkg-resources python3-ptyprocess python3-requests python3-six python3-speechd python3-urllib3 python3-xdg swaks xbrlapi Use 'apt autoremove' to remove them. The following additional packages will be installed: dma:i386 guile-2.0-libs libbz2-1.0:i386 libgpm2:i386 libgsasl7 libkyotocabinet16v5 libmailutils5 libmpdec2:i386 libncursesw5:i386 libntlm0 libpython3-stdlib:i386 libpython3.5-minimal:i386 libpython3.5-stdlib:i386 libreadline7:i386 libssl1.1:i386 libtinfo5:i386 mailutils-common python3:i386 python3-minimal:i386 python3.5:i386 python3.5-minimal:i386 Suggested packages: gpm:i386 mailutils-mh mailutils-doc python3-doc:i386 python3-tk:i386 python3-venv:i386 python3.5-venv:i386 python3.5-doc:i386 binutils:i386 binfmt-support:i386 The following packages will be REMOVED: apper apt-listchanges foomatic-db-compressed-ppds gdebi-core gdebi-kde gnome-orca hplip libreoffice libreoffice-librelogo libreoffice-script-provider-python openprinting-ppds opensmtpd:i386 printer-driver-dymo printer-driver-escpr printer-driver-foo2zjs printer-driver-foo2zjs-common printer-driver-fujixerox printer-driver-m2300w printer-driver-postscript-hp printer-driver-ptouch printer-driver-pxljr python3 python3-apt python3-brlapi python3-cairo python3-cups python3-cupshelpers python3-dbus python3-debianbts python3-gi python3-minimal python3-pil python3-pyatspi python3-pycurl python3-pykde4 python3-pyqt4 python3-pyqt5 python3-pysimplesoap python3-renderpm python3-reportbug python3-reportlab python3-reportlab-accel python3-sip python3-smbc python3-software-properties python3-uno python3.5 python3.5-minimal reportbug software-properties-common software-properties-kde system-config-printer system-config-printer-common system-config-printer-udev unattended-upgrades The following NEW packages will be installed: dma:i386 guile-2.0-libs libbz2-1.0:i386 libgpm2:i386 libgsasl7 libkyotocabinet16v5 libmailutils5 libmpdec2:i386 libncursesw5:i386 libntlm0 libpython3-stdlib:i386 libpython3.5-minimal:i386 libpython3.5-stdlib:i386 libreadline7:i386 libssl1.1:i386 libtinfo5:i386 mailutils mailutils-common python3:i386 python3-minimal:i386 python3.5:i386 python3.5-minimal:i386 0 upgraded, 22 newly installed, 55 to remove and 0 not upgraded. Need to get 11.7 MB of archives. After this operation, 58.7 MB disk space will be freed. Do you want to continue? [Y/n] Once I get my heart back in my chest, I respond "N" and abort the install... I USE python; I USE libreOffice; I USE gdebi... Why is this (supposedly) simple install removing so much of my system? | I would use synaptic and temporarily disable the majority of your sources.list, reload, and try again. |
I followed this guide https://wiki.debian.org/HowToUpgradeKernel that states: <!> Make sure you read everything it tells you during the installation, especially about initrd image. If you use an unusual boot loader, you might need to reconfigure after installing the kernel image - don't forget to tell it to use appropriate initrd image for the kernel in this case (PackageManagement page has details about listing contents of a package). My bootloader can be unusual, becasue there are 3 efi partitions. The system reported "Fail to load kernel modules" and the display manager didn' t start. The installation (apt-get install linux-image-4.18...) didn 't tell me anything. What do I need to do?. Also in the old kernel the display manager did' t start. I installed lightdm (via cli) and used it that for a while. I' m on debian 9 amd64. | Scorpion wrote:Code: Select all... 7: deb http://ftp.debian.org/debian stretch-backports main I installed the (384) nvidia drivers via backports Not with those sources. You need contrib non-free added to your backports line. I guess it defaulted to installing nvidia-driver from main which currently has 384.130-1. |
friends, bitlocker partition along with system reserved partition delays boot by quite some time. Trouble is I can not add these partitions to fstab as their uuid is not listed and for the system reserved partition even file type is not listed. my os version is current stable Debian Code: Select all├─sda1 vfat ESP F01C-09F5 ├─sda2 ├─sda3 ├─sda4 ext4 81018a48-1e98-4b33-bba2-da084709ef10 / ├─sda5 vfat NEW VOLUME 48EB-FB47 └─sda6 ntfs WINRETOOLS CECADF36CADF1A13 sda2 is the system reserved and 3 is the bitlocked one. I do not want to decrypt or mount the bitlocked partition. what i have tried? searched if hiding the partition in grub could help? but according to https://www.gnu.org/software/grub/manua ... ttool.html parttool seems to be valid only for mbr or dos partitions tables. i am on gpt. Appreciate your help. Thanks. | Why do you think the bitlocked partition is what is causing slow boot? |
Hi!I am running Debian 9.8 Stretch 64 bit. I have been periodically updating and upgrading my debian OS by running the command below apt update && apt upgrade Previously all updates have been running perfectly without any errors. However when I tried running the same command today,there are some repos that are producing hash mismatch errors below Err:4 http://security.debian.org/debian-security stretch/updates/main amd64 Packages Hash Sum mismatch Hashes of expected file: - Filesize:483756 [weak] - SHA256:c4de39d16ad1e8b52dd2537da46bcccf91d6b2592e8b421714abe3c238e03cef - SHA1:4dc344ec6a68a74867b75e8689a9effb8121fa3e [weak] - MD5Sum:2068534593f21de28583d36ca85b82b4 [weak] Hashes of received file: - SHA256:e2aac7ff8412613325cc542f77ce76a03ccad0c85048f356eee593a725a6c2bb - SHA1:bf01e2aa3bf966a74d6326d55a0978dc2f2b6d34 [weak] - MD5Sum:11dbe21bd766654e4cb54a4c797750eb [weak] - Filesize:483756 [weak] Last modification reported: Fri, 05 Apr 2019 21:17:45 +0000 Release file created at: Fri, 05 Apr 2019 21:17:56 +0000 E: Failed to fetch http://security.debian.org/debian-secur ... c238e03cef Hash Sum mismatch Hashes of expected file: - Filesize:483756 [weak] - SHA256:c4de39d16ad1e8b52dd2537da46bcccf91d6b2592e8b421714abe3c238e03cef - SHA1:4dc344ec6a68a74867b75e8689a9effb8121fa3e [weak] - MD5Sum:2068534593f21de28583d36ca85b82b4 [weak] Hashes of received file: - SHA256:e2aac7ff8412613325cc542f77ce76a03ccad0c85048f356eee593a725a6c2bb - SHA1:bf01e2aa3bf966a74d6326d55a0978dc2f2b6d34 [weak] - MD5Sum:11dbe21bd766654e4cb54a4c797750eb [weak] - Filesize:483756 [weak] Last modification reported: Fri, 05 Apr 2019 21:17:45 +0000 Release file created at: Fri, 05 Apr 2019 21:17:56 +0000 E: Some index files failed to download. They have been ignored, or old ones used instead. Kindly assist in resolving this. | LOL!The errors have disappeared after subsequent attempts to run the update upgrade command. Just wondering why the errors appeared in the first place.Maybe a connectivity problem to the repos in question? |
Hello to all, While using my preseed Debian Buster VM (which I actually upgraded from Debian Stretch), I have noticed the following problem, while trying to do update: user@unassigned-hostname:~/ebbchar$ uname -a Linux unassigned-hostname 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux user@unassigned-hostname:~/ebbchar$ su - Password: root@unassigned-hostname:~# pwd /root root@unassigned-hostname:~# cd /home/user/ebbchar/ root@unassigned-hostname:/home/user/ebbchar# apt update Hit:1 http://security.debian.org/debian-security buster/updates InRelease Ign:2 http://deb.debian.org/debian buster-backports InRelease Get:3 http://deb.debian.org/debian buster InRelease [158 kB] Err:4 http://deb.debian.org/debian buster-backports Release 404 Not Found [IP: 151.101.12.204 80] Get:5 http://deb.debian.org/debian buster/main amd64 Packages.diff/Index [27.9 kB] [snap] Get:21 http://http.us.debian.org/debian buster/main DEP-11 64x64 Icons [7,604 kB] Reading package lists... Done E: The repository 'http://deb.debian.org/debian buster-backports Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root@unassigned-hostname:/home/user/ebbchar# Since Debian Buster is still a pre-release, should I be worried about this ERROR, or the repository 'http://deb.debian.org/debian buster-backports" is still not yet set up properly? Thank you, _nobody_ | _nobody_ wrote:So, 09.2019 to 10.2019 is the release date. No. "When it's ready" is the release date. Anything else is speculation. Historically it's been around 6 months after full freeze which is what the speculation is based on. |
Having finally managed an update and getting my SMTP server working, the email server isn't receiving email. No error messages, but a generic failure message eventually arrives. Just nothing at the server end. There are no clues at all in the failure mail. Using dovecot and postfix, which was running fine on wheezy, but something must have changed on stretch - I just don't know what. MX records are fine and untouched. Any clues where I need to look? | At the failure message for a start. |
Hi!I am running Debian 9.8 Stretch 64 bit. I have been periodically updating and upgrading my debian OS by running the command below apt update && apt upgrade Previously all updates have been running perfectly without any errors. However when I tried running the same command today,I am getting Google earth repo invalid signatures as below Err:14 http://dl.google.com/linux/earth/deb stable Release.gpg The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com> W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/earth/deb stable Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com> W: Failed to fetch http://dl.google.com/linux/earth/deb/di ... elease.gpg The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com> W: Some index files failed to download. They have been ignored, or old ones used instead. Kindly assist in resolving this. | Wait for Google to update their key or take it up with them. See also http://forums.debian.net/viewtopic.php?f=6&t=141585 |
Hi, Did I get infected by a virus or a troyan? It's happening from a week or so, sometimes, suddenly The keyboard behave extrange, like with some kind of a lag, the Internet browser start to do some kind blinding and I cant't type properly anymore anywhere. I let the konsole by itself was typing alone that extrange character showed in capture... It happend just when waking up from sleep... It's happend more time (tree times or so) from some weeks ago. It gets fixed when I restart Plasma session.. I dont know what might it be, I dont remember what I might installed cos I have a very controlled and clean installation, I even use rollback btrfs snapshots system to mantain stable system.. but I have updated snapshot system with this virus included, and I cant rollback without getting away of this issue.. I just remember of installing in that period of time: - jpegoptim, bitwardern (deb), and some snaps - I was also always using an active(running) downgraded propietary java version (for java sticky app) >> I've just moved to openjdk and updated jdk - Im not using protection for snaps , neither for Meltdown and Spectre: GRUB_CMDLINE_LINUX_DEFAULT="apparmor=0 nopti noibrs noibpb" - Im using an old Opera version for so long (OperaV42) due to performance reasons I have some few packages retained due to believed performance and other kind of reasons.: Code: Select allLos siguientes paquetes se han retenido: dbus dbus-user-session dbus-x11 firefox-esr firefox-esr-l10n-es-es firmware-misc-nonfree g intel-microcode kde-style-qtcurve-qt4 kde-style-qtcurve-qt5 libdbus-1-3 libdbus-1-3:i386 l libudev1:i386 network-manager qtcurve qtcurve-l10n syslinux syslinux-common systemd-sysv u xserver-common xserver-xorg-core xserver-xorg-legacy Any suggestions , thanks | Have you tried using a different keyboard? Or plugging in an external keyboard if its a laptop? |
After upgrading from Stretch to Buster, my daily cron jobs started running at the wrong time (~7:40 AM instead of 6:25 AM). After some troubleshooting, I made a backup of my data and did a fresh install of Buster by installing from 9.7 media and then "apt full-upgrade". The problem persisted. I have not filed a bug report because I am not convinced that the problem isn't the stupid user (me). I will appreciate any advice. *** Hopefully Helpful Information *** The hardware is a 2011 iMac i5-2400s. Debian is the only installed OS and has been for the last ~eight years. The default entry in /etc/crontab is: 25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) If I change the entry to "25 1 * * * ...", the job still runs at (~7:40 AM). $ cat /etc/timezone America/New_York $ date; /sbin/hwclock Tue 12 Mar 2019 08:28:47 PM EDT 2019-03-12 20:28:47.358744-04:00 $ ps -ef | grep cron root 672 1 0 17:25 ? 00:00:00 /usr/sbin/cron -f $ dpkg -l '*cron*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-========================================= ii anacron 2.3-27 amd64 cron-like program that doesn't go by time ii cron 3.0pl1-132 amd64 process scheduling daemon un cron-daemon <none> <none> (no description available) | Anything in the journal? Code: Select alljournalctl -u cron |
A very nice feature in Windows was the ability to limit the charge of the Thinkpad to, say, 80% to preserve the battery. I would like to try the same in Debian. I know that this feature is quite hardware specific, so the solution you choose is likely not to work on different hardware. I have tested TLP. It works, but also breaks my screen brightness hotkey and the power management GUI in KDE. There are other solutions for pre-Sandy Bridge models, but the newer ones needs Tpacpi-bat to work. There is no Stretch package for it, so it has to be built from source. http://www.thinkwiki.org/wiki/Tpacpi-bat Does anyone else know of an easier/better way to make threshold charging possible? | stevepusser wrote:Rebuild the PPA packages from source on Stretch? That is probably a good idea, but it is a little above my head. |
Hi everyone, I rebooted my system as I do periodically, but this time it showed me a 'Boot Menu' I never saw before. I selected English, it seemed to go through the normal boot sequence, but then it froze at the splash screen instead of displaying a password prompt as it normally does. I did Ctrl+Alt+F1, the command prompt read "user@live-pc" instead of my user name. I tried su - <MYNAME> and got "No passwd entry for user '<MYNAME>' I tried to reboot, then boot in safe mode, but no difference. It's as if my username and login just disappeared?? I am confused, this behavior has never happened before. I was changing Samba share permissions at the time but I don't recall doing anything that could cause this. Thank you in advance for pointing me in the right direction. | Never mind... I unplugged the laptop, pulled the battery out, put it back in, restarted it... now it works. Weird. Sorry for the random post, hopefully it will help someone with the same trouble. Wish I understood what happened |
I have been trying to get samba working correctly and smoothly for years, so believe me, i've googled it. Now, I'm working with a fresh Debian 9 install and a win10 machine. I'm unable to access samba shares on my win10 machine, getting "permission denied" message. what is missing? I have Webmin installed thinking it would make the process easier. It has not. My samba config file (the relevant bits): Code: Select all# # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options most of which # are not shown in this example # # Some options that are often worth tuning have been included as # commented-out examples in this file. # - When such options are commented with ";", the proposed setting # differs from the default Samba behaviour # - When commented with "#", the proposed setting is the default # behaviour of Samba but the option is considered important # enough to be mentioned here # # NOTE: Whenever you modify this file you should run the command # "testparm" to check that you have not made any basic syntactic # errors. #======================= Global Settings ======================= [global] valid users = %S,maxTim,media,@maxTim,@media syslog = 0 max log size = 1000 passwd chat = *Enter\snew\s*\spassword:* %n *Retype\snew\s*\spassword:* %n *password\supdated\ssuccessfully* . os level = 20 passdb backend = tdbsam usershare allow guests = yes dns proxy = no server role = standalone server obey pam restrictions = yes panic action = /usr/share/samba/panic-action %d map to guest = bad user unix password sync = yes workgroup = WORKGROUP path = /home/media passwd program = /usr/bin/passwd %u log file = /var/log/samba/log.%m write list = maxTim,@maxTim pam password change = yes ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of # Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable its WINS Server # wins support = no # WINS Server - Tells the NMBD components of Samba to be a WINS Client # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both ; wins server = w.x.y.z # This will prevent nmbd to search for NetBIOS names through DNS. #### Networking #### # The specific set of interfaces / networks to bind to # This can be either the interface name or an IP address/netmask; # interface names are normally preferred ; interfaces = 127.0.0.0/8 eth0 # Only bind to the named interfaces and/or networks; you must use the # 'interfaces' option above to use this. # It is recommended that you enable this feature if your Samba machine is # not protected by a firewall or is a firewall itself. However, this # option cannot handle dynamic or non-broadcast interfaces correctly. ; bind interfaces only = yes #### Debugging/Accounting #### # This tells Samba to use a separate log file for each machine # that connects # Cap the size of the individual log files (in KiB). # If you want Samba to only log through syslog then set the following # parameter to 'yes'. # syslog only = no # We want Samba to log a minimum amount of information to syslog. Everything # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log # through syslog you should set the following parameter to something higher. # Do something sensible when Samba crashes: mail the admin a backtrace ####### Authentication ####### # Server role. Defines in which mode Samba will operate. Possible # values are "standalone server", "member server", "classic primary # domain controller", "classic backup domain controller", "active # directory domain controller". # # Most people will want "standalone sever" or "member server". # Running as "active directory domain controller" will require first # running "samba-tool domain provision" to wipe databases and create a # new domain. # If you are using encrypted passwords, Samba will need to know what # password database type you are using. # This boolean parameter controls whether Samba attempts to sync the Unix # password with the SMB password when the encrypted SMB password in the # passdb is changed. # For Unix password sync to work on a Debian GNU/Linux system, the following # parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for # sending the correct chat script for the passwd program in Debian Sarge). # This boolean controls whether PAM will be used for password changes # when requested by an SMB client instead of the program listed in # 'passwd program'. The default is 'no'. # This option controls how unsuccessful authentication attempts are mapped # to anonymous connections ########## Domains ########### # # The following settings only takes effect if 'server role = primary # classic domain controller', 'server role = backup domain controller' # or 'domain logons' is set # # It specifies the location of the user's # profile directory from the client point of view) The following # required a [profiles] share to be setup on the samba server (see # below) ; logon path = \\%N\profiles\%U # Another common choice is storing the profile in the user's home directory # (this is Samba's default) # logon path = \\%N\%U\profile # The following setting only takes effect if 'domain logons' is set # It specifies the location of a user's home directory (from the client # point of view) ; logon drive = H: # logon home = \\%N\%U # The following setting only takes effect if 'domain logons' is set # It specifies the script to run during logon. The script must be stored # in the [netlogon] share # NOTE: Must be store in 'DOS' file format convention ; logon script = logon.cmd # This allows Unix users to be created on the domain controller via the SAMR # RPC pipe. The example command creates a user account with a disabled Unix # password; please adapt to your needs ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u # This allows machine accounts to be created on the domain controller via the # SAMR RPC pipe. # The following assumes a "machines" group exists on the system ; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u # This allows Unix groups to be created on the domain controller via the SAMR # RPC pipe. ; add group script = /usr/sbin/addgroup --force-badname %g ############ Misc ############ # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting ; include = /home/samba/etc/smb.conf.%m # Some defaults for winbind (make sure you're not using the ranges # for something else.) ; idmap uid = 10000-20000 ; idmap gid = 10000-20000 ; template shell = /bin/bash # Setup usershare options to enable non-root users to share folders # with the net usershare command. # Maximum number of usershare. 0 (default) means that usershare is disabled. ; usershare max shares = 100 # Allow users who've been granted usershare privileges to create # public shares, not just authenticated ones #======================= Share Definitions ======================= [Media] comment = Media Share write list = maxTim,media,@maxTim,@media force create mode = 775 create mode = 0775 writeable = yes force directory mode = 775 valid users = %S,maxTim,media,@maxTim,@media directory mode = 0775 # By default, the home directories are exported read-only. Change the # next parameter to 'no' if you want to be able to write to them. # File creation mask is set to 0700 for security reasons. If you want to # create files with group=rw permissions, set next parameter to 0775. # Directory creation mask is set to 0700 for security reasons. If you want to # create dirs. with group=rw permissions, set next parameter to 0775. # By default, \\server\username shares can be connected to by anyone # with access to the samba server. # The following parameter makes sure that only "username" can connect # to \\server\username # This might need tweaking when using external authentication schemes # Un-comment the following and create the netlogon directory for Domain Logons # (you need to configure Samba to act as a domain controller too.) ;[netlogon] ; comment = Network Logon Service ; path = /home/samba/netlogon ; guest ok = yes ; read only = yes # Un-comment the following and create the profiles directory to store # users profiles (see the "logon path" option above) # (you need to configure Samba to act as a domain controller too.) # The path below should be writable by all users so that their # profile directory may be created the first time they log on ;[profiles] ; comment = Users profiles ; path = /home/samba/profiles ; guest ok = no ; browseable = no ; create mask = 0600 ; directory mask = 0700 [printers] comment = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = no read only = yes create mask = 0700 # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no # Uncomment to allow remote administration of Windows print drivers. # You may need to replace 'lpadmin' with the name of the group your # admin users are members of. # Please note that you also need to set appropriate Unix permissions # to the drivers directory for these users to have write rights in it ; write list = root, @lpadmin [maxTim] comment = maxTim Home Folder force group = maxTim force user = maxTim path = /home/maxTim valid users = @maxTim write list = @maxTim I have Code: Select allsmbpasswd -a maxTim and Code: Select allsmbpasswd -e maxTim What else do I need to do to make this work smoothly? Samba is the most frustrating thing for, me, btw. | maxTim wrote:What else do I need to do to make this work smoothly? Samba is the most frustrating thing for, me, btw. For a start, you could show us what the problem is? obviously including the relevant parts of the log. Note also that you should post the relevant parts of the configuration, not the whole fully-commented file. It's a pain to read. I attach my (working, with a Windows 10 client) configuration in debian buster: Code: Select all[global] workgroup = My_Workgroup server role = standalone disable netbios = yes security = user map to guest = Bad Password # the next 3 lines you probably don't need or in any case would need to adapt.. interfaces = 192.168.178.0/24 bind interfaces only = yes hosts allow = 192.168.178. load printers = no local master = yes logging = file log file = /var/log/smb.log log level = 1 max log size = 8192 server min protocol = SMB3 smb encrypt = desired use sendfile = yes [homes] comment = Home Directories path = /home/%u/smb valid users = @familie read only = No browseable = No create mask = 0750 directory mask = 0750 force create mode = 0640 force directory mode = 0750 force group = familie Adapt as necessary.. |
Hello Iam already on this issue several days, googled the heck out of it and engaged some other admins. Here ill try to be first only informative of the issue as it is, not to confuse it with all the unsuccessful methods i tried, so pleas bear with me :] I created SW RAID on debian server that is connected via JBOD controller to two expanders. The desired config is 10 RAID6 arrays and over each 2 of them, one RAID0 array - in the end its going to be 5 RAID60 arrays. This config already work on another, actually older server - so i have this tested, how to make it and just tried to reproduce it. Firstly since its all used disks, i ran sgdisk -Z on all of them, to clear GPT tables. It was not possible to run --zero-superblock since previously they were under HW RAID controller. The first 10 RAID6 arrays are working perfectly fine, they assemble no problem. Each has 6 disks, everything ok. After i assemble RAID0 each over two RAID6 arrays, its still ok. Arrays will start, ill update my /etc/mdadm/mdadm.conf and update initramfs. I can mount them, but iam not updating fstab since i know ill get stuck. You can see them in /proc/mdstat, you can see bklid or mdadm --details of it. Now after first reboot, if i check /proc/mdstat, all arrays were assembled. But i try second reboot in a row just in case and this time, only first 10 arrays of RAID6 are present and there is no trace of RAID0 arrays, except in /mdadm.conf. I noticed two things, you can see more in work log at the end of post: md8 : active (auto-read-only) - iam not sure i like auto-read-only status, i know its before first write onto to array, but what about the write of the supreblock of md8 when it was added to RAID0 afterwards. I already removed md11-15 onec, zero-superblock of md1-10 and then created the md11-15 again, from scratch, and for some reason, blkid showing its already xfs filesystem, that was there before. My bigest hopes are, that i just never completly wiped all mdadm raid configuration from whole system, and the system somehow, somewhere is trying to assemble different arrays. Hence output of dmesg when you MANUALLY assemble the arrays after bad reboot Code: Select all[ 485.058889] md: md11 stopped. [ 485.068868] md: bind<md2> [ 485.079243] md: bind<md1> [ 485.081216] md/raid0:md11: md_size is 46881636352 sectors. [ 485.081218] md: RAID0 configuration for md11 - 1 zone [ 485.081219] md: zone0=[md1/md2] [ 485.081250] md11: detected capacity change from 0 to 24003397812224 [ 486.215710] md: md14 stopped. [ 486.218076] md: bind<md8> [ 486.225730] md: bind<md7> [ 486.227535] md/raid0:md14: md_size is 46881636352 sectors. [ 486.227538] md: RAID0 configuration for md14 - 1 zone [ 486.227540] md: zone0=[md7/md8] [ 486.227577] md14: detected capacity change from 0 to 24003397812224 [ 487.326380] md: md15 stopped. [ 487.335260] md: bind<md10> [ 487.344579] md: bind<md9> [ 487.346600] md/raid0:md15: md_size is 46881636352 sectors. [ 487.346603] md: RAID0 configuration for md15 - 1 zone [ 487.346604] md: zone0=[md9/md10] [ 487.346639] md15: detected capacity change from 0 to 24003397812224 [ 488.426457] md: md13 stopped. [ 488.427639] md: bind<md6> [ 488.428949] md: bind<md5> [ 488.431399] md/raid0:md13: md_size is 46881636352 sectors. [ 488.431402] md: RAID0 configuration for md13 - 1 zone [ 488.431404] md: zone0=[md5/md6] [ 488.431443] md13: detected capacity change from 0 to 24003397812224 [ 489.552396] md: md12 stopped. [ 489.554881] md: bind<md4> [ 489.562527] md: bind<md3> [ 489.564898] md/raid0:md12: md_size is 46881636352 sectors. [ 489.564901] md: RAID0 configuration for md12 - 1 zone [ 489.564902] md: zone0=[md3/md4] [ 489.564937] md12: detected capacity change from 0 to 24003397812224 stopped? it was never started in a first place, so thats confusing I can provide full dmesg output, but what is seen, is just assemble of md1-10 and thats it, there is no attempt to assemble md1-10. Unless tried manually - as seen above. Here is a work log how it looks after bad reboot and how can you bring those RAID0 arrays back up, but after another reboot they are gone again. Code: Select allroot@server:~$ cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md8 : active (auto-read-only) raid6 sdat[2] sdas[1] sdav[4] sdau[3] sdar[0] sdaw[5] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md6 : active (auto-read-only) raid6 sdah[2] sdai[3] sdaj[4] sdak[5] sdaf[0] sdag[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md5 : active (auto-read-only) raid6 sdad[4] sdae[5] sdac[3] sdz[0] sdaa[1] sdab[2] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md3 : active (auto-read-only) raid6 sdo[1] sdp[2] sdq[3] sdr[4] sdn[0] sds[5] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md4 : active (auto-read-only) raid6 sdv[2] sdu[1] sdw[3] sdt[0] sdy[5] sdx[4] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md2 : active (auto-read-only) raid6 sdk[3] sdj[2] sdl[4] sdh[0] sdm[5] sdi[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md9 : active (auto-read-only) raid6 sdbc[5] sdax[0] sdaz[2] sdba[3] sdbb[4] sday[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md10 : active (auto-read-only) raid6 sdbh[4] sdbg[3] sdbe[1] sdbd[0] sdbi[5] sdbf[2] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md7 : active (auto-read-only) raid6 sdap[4] sdaq[5] sdao[3] sdan[2] sdal[0] sdam[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md1 : active (auto-read-only) raid6 sdb[0] sdg[5] sde[3] sdc[1] sdf[4] sdd[2] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk root@server:~# mdadm -D --scan ARRAY /dev/md/1 metadata=1.2 name=vod0-iva:1 UUID=1fa709ac:47d4e831:49b29e7a:380a198a ARRAY /dev/md/7 metadata=1.2 name=vod0-iva:7 UUID=36b01bb6:97a0095f:9e7a4d61:994e9577 ARRAY /dev/md/10 metadata=1.2 name=vod0-iva:10 UUID=5306e805:a8cf4af3:53b32a3a:445e277d ARRAY /dev/md/9 metadata=1.2 name=vod0-iva:9 UUID=bc7a0857:84f133c4:453dcc65:1ae11abe ARRAY /dev/md/2 metadata=1.2 name=vod0-iva:2 UUID=4993a3d5:f0a39e85:f8104370:aed5e951 ARRAY /dev/md/4 metadata=1.2 name=vod0-iva:4 UUID=d18b1263:fb902e8b:730f522a:db993f40 ARRAY /dev/md/3 metadata=1.2 name=vod0-iva:3 UUID=40de46c2:70c6e63f:e9576997:285c2ff3 ARRAY /dev/md/5 metadata=1.2 name=vod0-iva:5 UUID=5b6db0c0:53cb2714:4a982ac4:9a837cca ARRAY /dev/md/6 metadata=1.2 name=vod0-iva:6 UUID=183429d2:fb95b326:3016ab5c:6cd80d2f ARRAY /dev/md/8 metadata=1.2 name=vod0-iva:8 UUID=6918a7f7:e77b8f46:38cd4ff6:e3e16740 root@server:~# mdadm --assemble --scan mdadm: /dev/md/11 has been started with 2 drives. mdadm: /dev/md/14 has been started with 2 drives. mdadm: /dev/md/15 has been started with 2 drives. mdadm: /dev/md/13 has been started with 2 drives. mdadm: /dev/md/12 has been started with 2 drives. root@server:~# mdadm -D --scan ARRAY /dev/md/1 metadata=1.2 name=vod0-iva:1 UUID=1fa709ac:47d4e831:49b29e7a:380a198a ARRAY /dev/md/7 metadata=1.2 name=vod0-iva:7 UUID=36b01bb6:97a0095f:9e7a4d61:994e9577 ARRAY /dev/md/10 metadata=1.2 name=vod0-iva:10 UUID=5306e805:a8cf4af3:53b32a3a:445e277d ARRAY /dev/md/9 metadata=1.2 name=vod0-iva:9 UUID=bc7a0857:84f133c4:453dcc65:1ae11abe ARRAY /dev/md/2 metadata=1.2 name=vod0-iva:2 UUID=4993a3d5:f0a39e85:f8104370:aed5e951 ARRAY /dev/md/4 metadata=1.2 name=vod0-iva:4 UUID=d18b1263:fb902e8b:730f522a:db993f40 ARRAY /dev/md/3 metadata=1.2 name=vod0-iva:3 UUID=40de46c2:70c6e63f:e9576997:285c2ff3 ARRAY /dev/md/5 metadata=1.2 name=vod0-iva:5 UUID=5b6db0c0:53cb2714:4a982ac4:9a837cca ARRAY /dev/md/6 metadata=1.2 name=vod0-iva:6 UUID=183429d2:fb95b326:3016ab5c:6cd80d2f ARRAY /dev/md/8 metadata=1.2 name=vod0-iva:8 UUID=6918a7f7:e77b8f46:38cd4ff6:e3e16740 ARRAY /dev/md/11 metadata=1.2 name=vod0-iva:11 UUID=1c4c9c36:893be126:c7b593a1:b4d4d676 ARRAY /dev/md/14 metadata=1.2 name=vod0-iva:14 UUID=eae871a5:5be6ae31:15beb88a:79ec552a ARRAY /dev/md/15 metadata=1.2 name=vod0-iva:15 UUID=ebbe3e34:eb386e8d:b56aeade:0c0e68be ARRAY /dev/md/13 metadata=1.2 name=vod0-iva:13 UUID=47aa06fa:d0103ec5:286787da:e3682706 ARRAY /dev/md/12 metadata=1.2 name=vod0-iva:12 UUID=c3fe03dd:39df25a7:5ed7460c:266850f7 root@server:~# cat /etc/mdadm/mdadm.conf # mdadm.conf HOMEHOST <system> # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md/2 metadata=1.2 UUID=4993a3d5:f0a39e85:f8104370:aed5e951 name=vod0-iva:2 ARRAY /dev/md/3 metadata=1.2 UUID=40de46c2:70c6e63f:e9576997:285c2ff3 name=vod0-iva:3 ARRAY /dev/md/4 metadata=1.2 UUID=d18b1263:fb902e8b:730f522a:db993f40 name=vod0-iva:4 ARRAY /dev/md/6 metadata=1.2 UUID=183429d2:fb95b326:3016ab5c:6cd80d2f name=vod0-iva:6 ARRAY /dev/md/7 metadata=1.2 UUID=36b01bb6:97a0095f:9e7a4d61:994e9577 name=vod0-iva:7 ARRAY /dev/md/8 metadata=1.2 UUID=6918a7f7:e77b8f46:38cd4ff6:e3e16740 name=vod0-iva:8 ARRAY /dev/md/5 metadata=1.2 UUID=5b6db0c0:53cb2714:4a982ac4:9a837cca name=vod0-iva:5 ARRAY /dev/md/1 metadata=1.2 UUID=1fa709ac:47d4e831:49b29e7a:380a198a name=vod0-iva:1 ARRAY /dev/md/9 metadata=1.2 UUID=bc7a0857:84f133c4:453dcc65:1ae11abe name=vod0-iva:9 ARRAY /dev/md/10 metadata=1.2 UUID=5306e805:a8cf4af3:53b32a3a:445e277d name=vod0-iva:10 ARRAY /dev/md/11 metadata=1.2 UUID=1c4c9c36:893be126:c7b593a1:b4d4d676 name=vod0-iva:11 ARRAY /dev/md/14 metadata=1.2 UUID=eae871a5:5be6ae31:15beb88a:79ec552a name=vod0-iva:14 ARRAY /dev/md/15 metadata=1.2 UUID=ebbe3e34:eb386e8d:b56aeade:0c0e68be name=vod0-iva:15 ARRAY /dev/md/13 metadata=1.2 UUID=47aa06fa:d0103ec5:286787da:e3682706 name=vod0-iva:13 ARRAY /dev/md/12 metadata=1.2 UUID=c3fe03dd:39df25a7:5ed7460c:266850f7 name=vod0-iva:12 root@server:~# root@server:~# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md12 : active raid0 md3[0] md4[1] 23440818176 blocks super 1.2 512k chunks md13 : active raid0 md5[0] md6[1] 23440818176 blocks super 1.2 512k chunks md15 : active raid0 md9[0] md10[1] 23440818176 blocks super 1.2 512k chunks md14 : active raid0 md7[0] md8[1] 23440818176 blocks super 1.2 512k chunks md11 : active raid0 md1[0] md2[1] 23440818176 blocks super 1.2 512k chunks md8 : active (auto-read-only) raid6 sdat[2] sdas[1] sdav[4] sdau[3] sdar[0] sdaw[5] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md6 : active (auto-read-only) raid6 sdah[2] sdai[3] sdaj[4] sdak[5] sdaf[0] sdag[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md5 : active (auto-read-only) raid6 sdad[4] sdae[5] sdac[3] sdz[0] sdaa[1] sdab[2] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md3 : active (auto-read-only) raid6 sdo[1] sdp[2] sdq[3] sdr[4] sdn[0] sds[5] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md4 : active (auto-read-only) raid6 sdv[2] sdu[1] sdw[3] sdt[0] sdy[5] sdx[4] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md2 : active (auto-read-only) raid6 sdk[3] sdj[2] sdl[4] sdh[0] sdm[5] sdi[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md9 : active (auto-read-only) raid6 sdbc[5] sdax[0] sdaz[2] sdba[3] sdbb[4] sday[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md10 : active (auto-read-only) raid6 sdbh[4] sdbg[3] sdbe[1] sdbd[0] sdbi[5] sdbf[2] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md7 : active (auto-read-only) raid6 sdap[4] sdaq[5] sdao[3] sdan[2] sdal[0] sdam[1] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk md1 : active (auto-read-only) raid6 sdb[0] sdg[5] sde[3] sdc[1] sdf[4] sdd[2] 11720540160 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU] bitmap: 0/22 pages [0KB], 65536KB chunk unused devices: <none> root@:~# mdadm --detail /dev/md15 /dev/md15: Version : 1.2 Creation Time : Wed Feb 27 13:29:42 2019 Raid Level : raid0 Array Size : 23440818176 (22354.91 GiB 24003.40 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Wed Feb 27 13:29:42 2019 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Chunk Size : 512K Name : vod0-iva:15 (local to host vod0-iva) UUID : ebbe3e34:eb386e8d:b56aeade:0c0e68be Events : 0 Number Major Minor RaidDevice State 0 9 9 0 active sync /dev/md/9 1 9 10 1 active sync /dev/md/10 root@:~# fdisk -l /dev/md11 Disk /dev/md11: 21.9 TiB, 24003397812224 bytes, 46881636352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 524288 bytes / 2097152 bytes root@:~# fdisk -l /dev/md10 Disk /dev/md10: 10.9 TiB, 12001833123840 bytes, 23441080320 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 524288 bytes / 2097152 bytes | I have some new info AFTER i manually assemble the disks Code: Select allmdadm --assemble --scan and all looks good, i just in case update initramfs and check mdadm.conf is right, and reboot - the disks are ALL ASSEMBELED...now if i reboot again, md11-15 are lost, without any intervention from my side. here is output of dmesg after successful reboot. You can see that md1-10 and also md11-15 are assembled as they should. In previous post you can see they are simply not. Code: Select alldmseg | grep md Code: Select allroot@server:~# dmesg | grep md [ 0.000000] Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/vg.system-lv.root ro net.ifnames=0 biosdevname=0 rootdelay=60 quiet [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/vg.system-lv.root ro net.ifnames=0 biosdevname=0 rootdelay=60 quiet [ 2.585650] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.585789] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.585805] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.585822] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.692666] usb usb1: Manufacturer: Linux 4.9.0-6-amd64 ehci_hcd [ 2.716650] usb usb2: Manufacturer: Linux 4.9.0-6-amd64 ehci_hcd [ 7.839956] md: bind<sds> [ 7.841234] md: bind<sdb> [ 7.842259] md: bind<sdh> [ 7.843686] md: bind<sdf> [ 7.845037] md: bind<sdg> [ 7.850333] md: bind<sdi> [ 7.854045] md: bind<sdr> [ 7.855163] md: bind<sdk> [ 7.857139] md: bind<sdd> [ 7.859098] md: bind<sdj> [ 7.860771] md: bind<sdn> [ 7.862148] md: bind<sdo> [ 7.863710] md: bind<sdq> [ 7.865584] md: bind<sdm> [ 7.867552] md: bind<sdw> [ 7.868914] md: bind<sdab> [ 7.869959] md: bind<sdx> [ 7.871144] md: bind<sdu> [ 7.872750] md: bind<sdag> [ 7.874334] md: bind<sdl> [ 7.876187] md: bind<sdaa> [ 7.877642] md: bind<sdas> [ 7.878765] md: bind<sdaf> [ 7.879954] md: bind<sdt> [ 7.881564] md: bind<sdao> [ 7.882984] md: bind<sdv> [ 7.884996] md: bind<sdz> [ 7.886659] md: bind<sdac> [ 7.888273] md: bind<sdan> [ 7.889417] md: bind<sdaj> [ 7.890792] md: bind<sdap> [ 7.892203] md: bind<sdae> [ 7.894097] md: bind<sdp> [ 7.896086] md: bind<sdah> [ 7.897569] md: bind<sdar> [ 7.898914] md: bind<sde> [ 7.900901] md: bind<sdak> [ 7.902708] md: bind<sdy> [ 7.904794] md: bind<sdad> [ 7.906790] md: bind<sdal> [ 7.908442] md: bind<sdaq> [ 7.910551] md: bind<sdam> [ 7.912606] md: bind<sdc> [ 8.288070] md: raid6 personality registered for level 6 [ 8.288072] md: raid5 personality registered for level 5 [ 8.288072] md: raid4 personality registered for level 4 [ 8.288805] md/raid:md3: device sdp operational as raid disk 2 [ 8.288806] md/raid:md3: device sdq operational as raid disk 3 [ 8.288807] md/raid:md3: device sdo operational as raid disk 1 [ 8.288808] md/raid:md3: device sdn operational as raid disk 0 [ 8.288809] md/raid:md3: device sdr operational as raid disk 4 [ 8.288810] md/raid:md3: device sds operational as raid disk 5 [ 8.288994] md/raid:md5: device sdad operational as raid disk 4 [ 8.288995] md/raid:md5: device sdae operational as raid disk 5 [ 8.288996] md/raid:md5: device sdac operational as raid disk 3 [ 8.288997] md/raid:md5: device sdz operational as raid disk 0 [ 8.288998] md/raid:md5: device sdaa operational as raid disk 1 [ 8.288999] md/raid:md5: device sdab operational as raid disk 2 [ 8.289182] md/raid:md2: device sdl operational as raid disk 4 [ 8.289184] md/raid:md2: device sdm operational as raid disk 5 [ 8.289185] md/raid:md2: device sdj operational as raid disk 2 [ 8.289186] md/raid:md2: device sdk operational as raid disk 3 [ 8.289186] md/raid:md2: device sdi operational as raid disk 1 [ 8.289187] md/raid:md2: device sdh operational as raid disk 0 [ 8.289428] md/raid:md3: allocated 6490kB [ 8.289452] md/raid:md4: device sdy operational as raid disk 5 [ 8.289454] md/raid:md4: device sdv operational as raid disk 2 [ 8.289456] md/raid:md4: device sdt operational as raid disk 0 [ 8.289458] md/raid:md3: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 8.289462] md/raid:md4: device sdu operational as raid disk 1 [ 8.289470] md/raid:md4: device sdx operational as raid disk 4 [ 8.289476] md/raid:md4: device sdw operational as raid disk 3 [ 8.289570] created bitmap (22 pages) for device md3 [ 8.289597] md/raid:md5: allocated 6490kB [ 8.289602] md/raid:md1: device sdc operational as raid disk 1 [ 8.289603] md/raid:md1: device sde operational as raid disk 3 [ 8.289604] md/raid:md1: device sdd operational as raid disk 2 [ 8.289605] md/raid:md1: device sdg operational as raid disk 5 [ 8.289605] md/raid:md1: device sdf operational as raid disk 4 [ 8.289606] md/raid:md1: device sdb operational as raid disk 0 [ 8.289618] md/raid:md5: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 8.289699] created bitmap (22 pages) for device md5 [ 8.289771] md/raid:md2: allocated 6490kB [ 8.289813] md/raid:md2: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 8.289869] md/raid:md7: device sdam operational as raid disk 1 [ 8.289872] md/raid:md7: device sdaq operational as raid disk 5 [ 8.289874] md/raid:md7: device sdal operational as raid disk 0 [ 8.289875] md/raid:md7: device sdap operational as raid disk 4 [ 8.289877] md/raid:md7: device sdan operational as raid disk 2 [ 8.289878] md/raid:md7: device sdao operational as raid disk 3 [ 8.289902] created bitmap (22 pages) for device md2 [ 8.290039] md3: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 8.290106] md: bind<sdai> [ 8.290139] md/raid:md1: allocated 6490kB [ 8.290172] md/raid:md1: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 8.290181] md5: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 8.290268] created bitmap (22 pages) for device md1 [ 8.290367] md2: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 8.290396] md/raid:md4: allocated 6490kB [ 8.290434] md/raid:md4: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 8.290573] created bitmap (22 pages) for device md4 [ 8.290748] md1: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 8.290765] md/raid:md7: allocated 6490kB [ 8.290798] md/raid:md7: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 8.290935] created bitmap (22 pages) for device md7 [ 8.291350] md4: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 8.291676] md7: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 8.292768] md/raid:md6: device sdai operational as raid disk 3 [ 8.292770] md/raid:md6: device sdak operational as raid disk 5 [ 8.292770] md/raid:md6: device sdah operational as raid disk 2 [ 8.292771] md/raid:md6: device sdaj operational as raid disk 4 [ 8.292772] md/raid:md6: device sdaf operational as raid disk 0 [ 8.292773] md/raid:md6: device sdag operational as raid disk 1 [ 8.293247] md/raid:md6: allocated 6490kB [ 8.293484] md/raid:md6: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 8.293618] created bitmap (22 pages) for device md6 [ 8.294168] md6: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 8.298996] md4: detected capacity change from 0 to 12001833123840 [ 8.299000] md5: detected capacity change from 0 to 12001833123840 [ 8.299843] md3: detected capacity change from 0 to 12001833123840 [ 8.300837] md2: detected capacity change from 0 to 12001833123840 [ 8.302161] md7: detected capacity change from 0 to 12001833123840 [ 8.304114] md6: detected capacity change from 0 to 12001833123840 [ 8.313385] md1: detected capacity change from 0 to 12001833123840 [ 8.328640] md: bind<md2> [ 8.333243] md: bind<md3> [ 8.334610] md: bind<md6> [ 8.335849] md: bind<md7> [ 8.336785] md: bind<md4> [ 8.338428] md: raid0 personality registered for level 0 [ 8.338971] md/raid0:md12: md_size is 46881636352 sectors. [ 8.338973] md: RAID0 configuration for md12 - 1 zone [ 8.338974] md: zone0=[md3/md4] [ 8.338993] md12: detected capacity change from 0 to 24003397812224 [ 8.341812] md: bind<md5> [ 8.343597] md/raid0:md13: md_size is 46881636352 sectors. [ 8.343599] md: RAID0 configuration for md13 - 1 zone [ 8.343600] md: zone0=[md5/md6] [ 8.343619] md13: detected capacity change from 0 to 24003397812224 [ 8.344348] md: bind<md1> [ 8.345936] md/raid0:md11: md_size is 46881636352 sectors. [ 8.345938] md: RAID0 configuration for md11 - 1 zone [ 8.345940] md: zone0=[md1/md2] [ 8.345976] md11: detected capacity change from 0 to 24003397812224 [ 8.906892] md: bind<sdat> [ 9.735687] md: bind<sdau> [ 9.752229] md: bind<sdav> [ 9.770932] md: bind<sdax> [ 9.789371] md: bind<sdaw> [ 9.794732] md/raid:md8: device sdaw operational as raid disk 5 [ 9.794735] md/raid:md8: device sdav operational as raid disk 4 [ 9.794736] md/raid:md8: device sdau operational as raid disk 3 [ 9.794738] md/raid:md8: device sdat operational as raid disk 2 [ 9.794740] md/raid:md8: device sdar operational as raid disk 0 [ 9.794741] md/raid:md8: device sdas operational as raid disk 1 [ 9.795682] md/raid:md8: allocated 6490kB [ 9.795800] md/raid:md8: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 9.796087] created bitmap (22 pages) for device md8 [ 9.797111] md8: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 9.820586] md8: detected capacity change from 0 to 12001833123840 [ 9.821510] md: bind<sday> [ 9.826406] md: bind<sdba> [ 9.829572] md: bind<sdaz> [ 9.857463] md: bind<md8> [ 9.859338] md/raid0:md14: md_size is 46881636352 sectors. [ 9.859341] md: RAID0 configuration for md14 - 1 zone [ 9.859342] md: zone0=[md7/md8] [ 9.859372] md14: detected capacity change from 0 to 24003397812224 [ 9.877959] md: bind<sdbb> [ 9.881573] md: bind<sdbd> [ 9.904286] md: bind<sdbc> [ 9.909531] md/raid:md9: device sdbc operational as raid disk 5 [ 9.909534] md/raid:md9: device sdbb operational as raid disk 4 [ 9.909536] md/raid:md9: device sdaz operational as raid disk 2 [ 9.909538] md/raid:md9: device sdba operational as raid disk 3 [ 9.909540] md/raid:md9: device sday operational as raid disk 1 [ 9.909541] md/raid:md9: device sdax operational as raid disk 0 [ 9.910506] md/raid:md9: allocated 6490kB [ 9.910653] md/raid:md9: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 9.910941] created bitmap (22 pages) for device md9 [ 9.912040] md9: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 9.932901] md: bind<sdbf> [ 9.939683] md9: detected capacity change from 0 to 12001833123840 [ 9.946636] md: bind<sdbe> [ 9.977714] md: bind<sdbg> [ 9.981245] md: bind<md9> [ 9.999119] md: bind<sdbh> [ 10.010988] md: bind<sdbi> [ 10.017353] md/raid:md10: device sdbi operational as raid disk 5 [ 10.017355] md/raid:md10: device sdbh operational as raid disk 4 [ 10.017357] md/raid:md10: device sdbg operational as raid disk 3 [ 10.017358] md/raid:md10: device sdbe operational as raid disk 1 [ 10.017360] md/raid:md10: device sdbf operational as raid disk 2 [ 10.017362] md/raid:md10: device sdbd operational as raid disk 0 [ 10.018379] md/raid:md10: allocated 6490kB [ 10.018560] md/raid:md10: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 10.018822] created bitmap (22 pages) for device md10 [ 10.019922] md10: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 10.053567] md10: detected capacity change from 0 to 12001833123840 [ 10.096981] md: bind<md10> [ 10.099153] md/raid0:md15: md_size is 46881636352 sectors. [ 10.099156] md: RAID0 configuration for md15 - 1 zone [ 10.099157] md: zone0=[md9/md10] [ 10.099198] md15: detected capacity change from 0 to 24003397812224 [ 14.413950] md: linear personality registered for level -1 [ 14.417196] md: multipath personality registered for level -4 [ 14.421056] md: raid1 personality registered for level 1 [ 14.427081] md: raid10 personality registered for level 10 [ 78.544903] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 78.545923] systemd[1]: Detected architecture x86-64. [ 78.547136] systemd[1]: Set hostname to <vod0-iva>. [ 78.736238] systemd[1]: [/usr/lib/systemd/system/tv-4net-vodserver.service:17] Unknown lvalue 'RuntimeDirectoryPreserve' in section 'Service' [ 78.757684] systemd[1]: [/lib/systemd/system/redis-server.service:14] Unknown lvalue 'RunTimeDirectory' in section 'Service' [ 78.765604] systemd[1]: Listening on Journal Socket (/dev/log). [ 78.765879] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 78.765955] systemd[1]: Listening on udev Kernel Socket. [ 78.766045] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 78.766123] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 79.627104] systemd-journald[1859]: Received request to flush runtime journal from PID 1 Here in case, the same log, after unsecfull reboot (right after previous one, no action was taken, only update iniramfs in case and reboot) Code: Select all 0.000000] Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/vg.system-lv.root ro net.ifnames=0 biosdevname=0 rootdelay=60 quiet [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/vg.system-lv.root ro net.ifnames=0 biosdevname=0 rootdelay=60 quiet [ 2.486277] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.486453] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.486473] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.486494] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 2.595674] usb usb1: Manufacturer: Linux 4.9.0-6-amd64 ehci_hcd [ 2.615628] usb usb2: Manufacturer: Linux 4.9.0-6-amd64 ehci_hcd [ 7.438628] md: bind<sdy> [ 7.442624] md: bind<sdl> [ 7.445058] md: bind<sdal> [ 7.446676] md: bind<sdba> [ 7.448330] md: bind<sdai> [ 7.449774] md: bind<sdg> [ 7.451732] md: bind<sdat> [ 7.454676] md: bind<sdax> [ 7.455976] md: bind<sdx> [ 7.457628] md: bind<sdt> [ 7.460602] md: bind<sdd> [ 7.461894] md: bind<sdq> [ 7.463687] md: bind<sdbi> [ 7.465280] md: bind<sdu> [ 7.467792] md: bind<sdb> [ 7.470092] md: bind<sdj> [ 7.471408] md: bind<sdbd> [ 7.473248] md: bind<sdaa> [ 7.476721] md: bind<sdaf> [ 7.479889] md: bind<sdi> [ 7.481714] md: bind<sdbf> [ 7.485811] md: bind<sds> [ 7.488130] md: bind<sdaq> [ 7.490387] md: bind<sdbb> [ 7.493194] md: bind<sdv> [ 7.497142] md: bind<sdh> [ 7.499072] md: bind<sdp> [ 7.500560] md: bind<sdaz> [ 7.502276] md: bind<sdac> [ 7.503598] md: bind<sdan> [ 7.505120] md: bind<sday> [ 7.506931] md: bind<sdad> [ 7.508423] md: bind<sdao> [ 7.509926] md: bind<sdau> [ 7.511230] md: bind<sdab> [ 7.513200] md: bind<sdr> [ 7.514833] md: bind<sdaj> [ 7.516547] md: bind<sdf> [ 7.518578] md: bind<sdk> [ 7.521002] md: bind<sdw> [ 7.523507] md: bind<sdo> [ 7.526058] md: bind<sdn> [ 7.528546] md: bind<sdc> [ 7.530897] md: bind<sdbe> [ 7.532990] md: bind<sdav> [ 7.534540] md: bind<sdak> [ 7.536557] md: bind<sdaw> [ 7.538637] md: bind<sdap> [ 7.540921] md: bind<sdar> [ 7.543204] md: bind<sdz> [ 7.545528] md: bind<sdbg> [ 7.548065] md: bind<sdbh> [ 7.550487] md: bind<sde> [ 7.553557] md: bind<sdbc> [ 7.555959] md: bind<sdah> [ 7.558529] md: bind<sdm> [ 7.561065] md: bind<sdag> [ 7.563620] md: bind<sdae> [ 7.565793] md: bind<sdas> [ 7.568067] md: bind<sdam> [ 7.936558] md: raid6 personality registered for level 6 [ 7.936559] md: raid5 personality registered for level 5 [ 7.936560] md: raid4 personality registered for level 4 [ 7.937477] md/raid:md2: device sdm operational as raid disk 5 [ 7.937480] md/raid:md2: device sdk operational as raid disk 3 [ 7.937483] md/raid:md2: device sdh operational as raid disk 0 [ 7.937484] md/raid:md2: device sdi operational as raid disk 1 [ 7.937486] md/raid:md2: device sdj operational as raid disk 2 [ 7.937488] md/raid:md2: device sdl operational as raid disk 4 [ 7.937694] md/raid:md4: device sdw operational as raid disk 3 [ 7.937697] md/raid:md4: device sdv operational as raid disk 2 [ 7.937698] md/raid:md4: device sdu operational as raid disk 1 [ 7.937699] md/raid:md4: device sdt operational as raid disk 0 [ 7.937701] md/raid:md4: device sdx operational as raid disk 4 [ 7.937702] md/raid:md4: device sdy operational as raid disk 5 [ 7.937944] md/raid:md5: device sdae operational as raid disk 5 [ 7.937947] md/raid:md5: device sdz operational as raid disk 0 [ 7.937948] md/raid:md5: device sdab operational as raid disk 2 [ 7.937950] md/raid:md5: device sdad operational as raid disk 4 [ 7.937951] md/raid:md5: device sdac operational as raid disk 3 [ 7.937952] md/raid:md5: device sdaa operational as raid disk 1 [ 7.938217] md/raid:md7: device sdam operational as raid disk 1 [ 7.938220] md/raid:md7: device sdap operational as raid disk 4 [ 7.938222] md/raid:md7: device sdao operational as raid disk 3 [ 7.938224] md/raid:md7: device sdan operational as raid disk 2 [ 7.938226] md/raid:md7: device sdaq operational as raid disk 5 [ 7.938228] md/raid:md7: device sdal operational as raid disk 0 [ 7.938473] md/raid:md10: device sdbh operational as raid disk 4 [ 7.938476] md/raid:md10: device sdbg operational as raid disk 3 [ 7.938478] md/raid:md10: device sdbe operational as raid disk 1 [ 7.938480] md/raid:md10: device sdbf operational as raid disk 2 [ 7.938482] md/raid:md10: device sdbd operational as raid disk 0 [ 7.938485] md/raid:md10: device sdbi operational as raid disk 5 [ 7.938714] md/raid:md4: allocated 6490kB [ 7.938756] md/raid:md4: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.938761] md/raid:md8: device sdas operational as raid disk 1 [ 7.938766] md/raid:md8: device sdar operational as raid disk 0 [ 7.938768] md/raid:md8: device sdaw operational as raid disk 5 [ 7.938774] md/raid:md8: device sdav operational as raid disk 4 [ 7.938777] md/raid:md8: device sdau operational as raid disk 3 [ 7.938780] md/raid:md8: device sdat operational as raid disk 2 [ 7.938844] md/raid:md2: allocated 6490kB [ 7.938880] md/raid:md2: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.938896] created bitmap (22 pages) for device md4 [ 7.939026] created bitmap (22 pages) for device md2 [ 7.939054] md/raid:md5: allocated 6490kB [ 7.939061] md/raid:md3: device sdn operational as raid disk 0 [ 7.939064] md/raid:md3: device sdo operational as raid disk 1 [ 7.939066] md/raid:md3: device sdr operational as raid disk 4 [ 7.939068] md/raid:md3: device sdp operational as raid disk 2 [ 7.939070] md/raid:md3: device sds operational as raid disk 5 [ 7.939072] md/raid:md3: device sdq operational as raid disk 3 [ 7.939090] md/raid:md5: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.939224] created bitmap (22 pages) for device md5 [ 7.939355] md/raid:md1: device sde operational as raid disk 3 [ 7.939357] md/raid:md1: device sdc operational as raid disk 1 [ 7.939358] md/raid:md1: device sdf operational as raid disk 4 [ 7.939360] md/raid:md1: device sdb operational as raid disk 0 [ 7.939361] md/raid:md1: device sdd operational as raid disk 2 [ 7.939362] md/raid:md1: device sdg operational as raid disk 5 [ 7.939621] md4: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.939623] md/raid:md6: device sdag operational as raid disk 1 [ 7.939626] md/raid:md6: device sdah operational as raid disk 2 [ 7.939628] md/raid:md6: device sdak operational as raid disk 5 [ 7.939630] md/raid:md6: device sdaj operational as raid disk 4 [ 7.939632] md/raid:md6: device sdaf operational as raid disk 0 [ 7.939634] md/raid:md6: device sdai operational as raid disk 3 [ 7.939695] md/raid:md7: allocated 6490kB [ 7.939775] md/raid:md7: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.939914] md/raid:md9: device sdbc operational as raid disk 5 [ 7.939916] created bitmap (22 pages) for device md7 [ 7.939918] md/raid:md9: device sday operational as raid disk 1 [ 7.939920] md/raid:md9: device sdaz operational as raid disk 2 [ 7.939922] md/raid:md9: device sdbb operational as raid disk 4 [ 7.939924] md/raid:md9: device sdax operational as raid disk 0 [ 7.939926] md/raid:md9: device sdba operational as raid disk 3 [ 7.939966] md2: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.940001] md5: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.940007] md/raid:md10: allocated 6490kB [ 7.940100] md/raid:md10: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.940215] md/raid:md8: allocated 6490kB [ 7.940240] created bitmap (22 pages) for device md10 [ 7.940294] md/raid:md8: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.940415] created bitmap (22 pages) for device md8 [ 7.940552] md/raid:md3: allocated 6490kB [ 7.940645] md/raid:md1: allocated 6490kB [ 7.940708] md/raid:md1: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.940713] md/raid:md3: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.940758] md/raid:md6: allocated 6490kB [ 7.940772] md7: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.940809] md/raid:md6: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.940843] created bitmap (22 pages) for device md1 [ 7.940850] created bitmap (22 pages) for device md3 [ 7.940889] md/raid:md9: allocated 6490kB [ 7.940912] created bitmap (22 pages) for device md6 [ 7.940923] md/raid:md9: raid level 6 active with 6 out of 6 devices, algorithm 2 [ 7.941031] created bitmap (22 pages) for device md9 [ 7.941141] md10: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.941300] md8: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.941477] md1: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.941479] md3: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.941552] md6: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.941644] md9: bitmap initialized from disk: read 2 pages, set 0 of 44711 bits [ 7.949656] md2: detected capacity change from 0 to 12001833123840 [ 7.950026] md5: detected capacity change from 0 to 12001833123840 [ 7.950057] md4: detected capacity change from 0 to 12001833123840 [ 7.950078] md7: detected capacity change from 0 to 12001833123840 [ 7.950289] md8: detected capacity change from 0 to 12001833123840 [ 7.951127] md6: detected capacity change from 0 to 12001833123840 [ 7.951943] md3: detected capacity change from 0 to 12001833123840 [ 7.971509] md1: detected capacity change from 0 to 12001833123840 [ 7.976157] md10: detected capacity change from 0 to 12001833123840 [ 8.006509] md9: detected capacity change from 0 to 12001833123840 [ 11.969703] md: linear personality registered for level -1 [ 11.972694] md: multipath personality registered for level -4 [ 11.975048] md: raid0 personality registered for level 0 [ 11.977687] md: raid1 personality registered for level 1 [ 11.984865] md: raid10 personality registered for level 10 |
Hi there everybody, I have just switched to Debian and I'm having problems setting my screen resolution, 1920x1080 for an Acer K22HQL. I have posted the verbose xrandr as well as the lspci and lsmod below. I have tried using the in-forum search system and online searching. Sadly, I have yet to find a successful resolution to this issue. I hope someone can help. Cheers! Code: Select all:~$ xrandr --verbose xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected primary 1024x768+0+0 (0x270) normal (normal) 0mm x 0mm Identifier: 0x26f Timestamp: 17612 Subpixel: unknown Clones: CRTC: 0 CRTCs: 0 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: _MUTTER_PRESENTATION_OUTPUT: 0 1024x768 (0x270) 59.769MHz *current h: width 1024 start 0 end 0 total 1024 skew 0 clock 58.37KHz v: height 768 start 0 end 0 total 768 clock 76.00Hz Code: Select all:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15d0 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 15d1 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15d3 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15db 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15dc 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e8 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e9 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ea 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15eb 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ec 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ed 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ee 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ef 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43bb (rev 02) 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b7 (rev 02) 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b2 (rev 02) 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) 02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02) 03:00.0 USB controller: ASMedia Technology Inc. Device 1343 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 15dd (rev c6) 08:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 15de 08:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 15df 08:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15e0 08:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15e1 08:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Device 15e3 09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61) Code: Select all:~$ lsmod Module Size Used by fuse 98304 3 rfcomm 77824 2 cmac 16384 1 bnep 20480 2 nls_ascii 16384 1 nls_cp437 20480 1 vfat 20480 1 fat 69632 1 vfat arc4 16384 2 rtl8192ee 98304 0 btcoexist 53248 1 rtl8192ee rtl_pci 28672 1 rtl8192ee rtlwifi 77824 2 rtl8192ee,rtl_pci btusb 45056 0 mac80211 671744 3 rtl8192ee,rtl_pci,rtlwifi btrtl 16384 1 btusb btbcm 16384 1 btusb eeepc_wmi 16384 0 btintel 16384 1 btusb asus_wmi 28672 1 eeepc_wmi sparse_keymap 16384 1 asus_wmi bluetooth 552960 31 btrtl,btintel,bnep,btbcm,rfcomm,btusb snd_hda_codec_realtek 90112 1 joydev 20480 0 snd_hda_codec_generic 69632 1 snd_hda_codec_realtek evdev 24576 15 cfg80211 589824 2 mac80211,rtlwifi snd_hda_codec_hdmi 49152 1 rfkill 24576 7 asus_wmi,bluetooth,cfg80211 snd_hda_intel 36864 10 snd_hda_codec 135168 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek kvm 598016 0 sg 32768 0 snd_hda_core 90112 5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek snd_hwdep 16384 1 snd_hda_codec irqbypass 16384 1 kvm snd_pcm 110592 5 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi efi_pstore 16384 0 crct10dif_pclmul 16384 0 snd_timer 32768 1 snd_pcm crc32_pclmul 16384 0 snd 86016 27 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm soundcore 16384 1 snd ghash_clmulni_intel 16384 0 pcspkr 16384 0 serio_raw 16384 0 shpchp 36864 0 sp5100_tco 16384 0 efivars 20480 1 efi_pstore wmi 16384 1 asus_wmi video 40960 1 asus_wmi button 16384 0 acpi_cpufreq 20480 0 efivarfs 16384 1 ip_tables 24576 0 x_tables 36864 1 ip_tables autofs4 40960 2 ext4 585728 2 crc16 16384 2 bluetooth,ext4 jbd2 106496 1 ext4 crc32c_generic 16384 0 fscrypto 28672 1 ext4 ecb 16384 0 mbcache 16384 3 ext4 dm_mod 118784 6 sr_mod 24576 0 sd_mod 49152 6 cdrom 61440 1 sr_mod hid_generic 16384 0 usbhid 53248 0 hid 122880 2 hid_generic,usbhid crc32c_intel 24576 2 aesni_intel 167936 2 aes_x86_64 20480 1 aesni_intel glue_helper 16384 1 aesni_intel lrw 16384 1 aesni_intel gf128mul 16384 1 lrw ablk_helper 16384 1 aesni_intel cryptd 24576 3 ablk_helper,ghash_clmulni_intel,aesni_intel psmouse 135168 0 i2c_piix4 24576 0 ahci 40960 4 libahci 32768 1 ahci r8169 86016 0 mii 16384 1 r8169 xhci_pci 16384 0 libata 249856 2 ahci,libahci xhci_hcd 188416 1 xhci_pci usbcore 253952 4 usbhid,xhci_pci,btusb,xhci_hcd scsi_mod 225280 4 sd_mod,libata,sr_mod,sg usb_common 16384 1 usbcore | AMD gpu requires some non-free firmware. Are they installed? https://wiki.debian.org/AtiHowTo#Firmware |
Hi to all, I'm trying to resolve a problem with my server but I can't find the real problem! Actually the server, during the reboot or shutdown phase, take a lot of time but only if the server is up from about half day! I tried to lock inside the journalctl but I can't see nothing, at least my eye does not catch it! I only see that the watchdog daemon hit the 10 minutes, actually they're 20! Then the reboot happen! I read around that the watchdog daemon is only a trigger so this's normal! There's any way to have a more detailed log for the shutdown phase in order to see what make the server hanging on? I put the link to the reboot log, maybe some more expert user can see what is escaping to me! https://pastebin.com/pXbd5UT0 Jo | Chryses wrote:There's any way to have a more detailed log for the shutdown phase in order to see what make the server hanging on? https://freedesktop.org/wiki/Software/s ... /#index2h1 EDIT: that "transport endpoint is not connected" error suggests a mounting problem (f'nar), try adding x.systemd.automount to the options for any external drive or file shares in /etc/fstab (or post your fstab). |
There are many different solutions for this in google but nothing works and are not for Debian.. While starting my machine I get 2 problems: 1. Flip done time out 2. Time difference I have windows 7 in dual boot on different hard disk space. The time and date on my Debian, Windows 7 and BIOS are same. Error 1: {48.695823} drm:drm_automic_helper_wait_for_dependencies {drm_kms_helper}} *Error* {connector:50:svideo-1} flip_done time out Error 2: Superblock last mount time is in the future. {by less than a day, probably due to hardware clock being incorrectly set} clean, 188644/8151040 files, 17958064/32583168 blocks This error was with Debian 9 Stretch and now I have upgraded to Debian 10 testing but the problem is still there Please help. | Either set Debian to use localtime or set Windows to use UTC. |
I have Googled a full night but get nowhere. Everything works fine in 1280x1024 if I use a short VGA cable, but I need 14 m cable so I use a VGA to HDMI to DVI solution. If I boot with the VGA cable I can then switch to the VGA/HDMI/DVI cable and everything is still good. But if I restart and boot with VGA/HDMI/DVI I can as most get 1024x768. There must be a way to force Debian to output 1280x1024. I know it can work since It does if I switch the cable after boot. GRUB_GFXMODE does not work, the screen is black during boot and wakes up at login with 1024x768. vga=794 shows sporadic text during boot, probably at 1280x1024 but goes black and changes to 1024x768 before login. VGA is flawless with the attached grub file. It feels like there is an auto sensing of the screen that sets the correct or wrong resolution after GRUB. It seems I must use nomodeset to force the VESA driver because with the intel driver my USB mouse does not work with either cable. Below are INXI and xrandr outputs and the GRUB file. Code: Select all///////////////////////////////////////////////////////////////////////////////////////////////////////// Screen: HP L1950g // What xrandr outputs when booted with VGA but after changing cable to VGA/HDMI/DVI. xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 0.0* 1024x768 0.0 800x600 0.0 640x480 0.0 // What xrandr outputs after restarting and booting with VGA/HDMI/DVI. xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 0mm x 0mm 1024x768 61.0* 800x600 61.0 640x480 60.0 ///////////////////////////////////////////////////////////////////////////////////////////////////////// // The GRUB file. # 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="lapic quiet splash rootdelay=5 idle=poll nomodeset" GRUB_CMDLINE_LINUX="initrd=/install/gtk/initrd.gz" # 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 #GRUB_GFXMODE=1280x1024 #GRUB_GFXPAYLOAD_LINUX=keep # 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" ///////////////////////////////////////////////////////////////////////////////////////////////////////// patrik@debian:~$ sudo inxi -F all [sudo] password for patrik: System: Host: debian Kernel: 3.4-9-rtai-686-pae i686 (32 bit) Desktop: Xfce 4.8.3 Distro: Debian GNU/Linux 7 (wheezy) Machine: Device: desktop System: Hewlett-Packard product: HP Compaq dc7700p Small Form Factor serial: HUB72513S5 Mobo: Hewlett-Packard model: 0A54h serial: HUB72513S5 BIOS: Hewlett-Packard v: 786E1 v02.10 date: 04/13/2007 CPU: Dual core Intel Core2 6300 (-MCP-) cache: 2048 KB clock speeds: max: 1862 MHz 1: 1862 MHz 2: 1862 MHz Graphics: Card: Intel 82Q963/Q965 Integrated Graphics Controller Display Server: X.org 1.12.4 drivers: vesa,intel (unloaded: fbdev) tty size: 125x36 Advanced Data: N/A for root Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel Sound: ALSA v: 1.0.25 Network: Card: Intel 82566DM Gigabit Network Connection driver: e1000e IF: eth0 state: down mac: 00:1b:78:87:7d:92 Drives: HDD Total Size: 80.0GB (9.5% used) ID-1: /dev/sda model: Hitachi_HDS72168 size: 80.0GB Partition: ID-1: / size: 71G used: 4.2G (7%) fs: ext4 dev: /dev/sda1 ID-2: swap-1 size: 3.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda5 Sensors: System Temperatures: cpu: 50.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 114 Uptime: 16 min Memory: 175.5/3526.1MB Client: Shell (sudo) inxi: 2.3.8 ///////////////////////////////////////////////////////////////////////////////////////////////////////// I have only VGA out from the intel graphics and VGA or DVI in to the HP L1950g screen. | There must be a way to force Debian to output 1280x1024. https://www.youtube.com/watch?v=MScLD8dFNwk ? |
Hi everybody, The question seems to be simple but I have a problem : I have a DTB file that is mandatory to boot my ARM64 computer. And I fail at trying to tell him to use it ! On the ISO at side of the "vmLinuz" and "initrd.gz" file, i've placed the "msm8998-mtp.dtb" file. grub.cfg interesting part : Code: Select allmenuentry 'Linux 4.20 No ACPI build MSM8998 DTB' { set background_color=black linux /install.a64/vmLinuz --- dtb=/install.a64/msm8998-mtp.dtb initrd /install.a64/initrd.gz } When trying this, kernel tells me "Failed to handle fs_proto". I guess /install.a64/ is only visible from GRUB, but not from the Kernel. Also, I think it's a CDROM Filesystem, because it's an ISO file I'm placing on the USB Key with dd. But I guess Linux know what a CD-ROM filesystem is ! I have to give this DTB file to the Kernel, if not it has no chance to boot. When it's saying "using DTB from configuration table" it's not going to work (somebody told me that the DTB inside the UEFI Configuration Tables is not complete enough on this device), I have to read "using DTB from command line" into the feedback. I'm failing at that which is pretty sad and frustrating. I get an error message saying "Failed to handle fs_proto" when I try to give the address of the file. It makes no differences if the adress is valid or invalid, which probably means I have to use a precise syntax in order to have Linux looking into the good device>file system, at the correct folder... But I don't know which syntax and searching on the Internet gives anything but that... Thank you in advance ! EDIT : after a lot of frustrating searches telling me uninteresting things over hundreds of pages, I'm back to this page talking about "dtb=" command. https://www.kernel.org/doc/Documentation/efi-stub.txt but giving some clues some lines upper, into initrd explanations. It seems that the syntax (at least for initrd) should be with backslashes and can only be relative to ESP root... However my DTB file is not into ESP root so I'll try to find a way to add it by moving / resizing partitions of the ISO (hoping that GRUB will still be able to find its files) in order to add my file on it. If not I will try to add fs0, fs1, fs2, or fs0:\, fs1:\, fs2:\... and hope that Linux would be able to understand what I'm talking about ! I'll keep you informed | EFI_STUB booting requires that the kernel image & intramfs also be on the ESP. I'm not familiar with arm64 but does this help: https://superuser.com/questions/736500/ ... leboard-xm |
Hi, I need some help, I took a look at internet seeking for this, but I didnt find much very good information about it, I tried some proposals solutions but they didnt work at all, so I came here for some help of you, I know this mustn't be any difficult, so where and How do I have to go about setting thoses scripts in order to be launching on waking up or/and on suspending the system. Thanks a lot. | Ways I can think of off the top of my head.. /lib/systemd/system-sleep - check man systemd-sleep /usr/lib/pm-utils/sleep.d or /etc/pm - might or might not need pm-utils pkg /etc/acpi - catch a lid or power event, probably some examples there already use laptop-mode or some other power mgr, not too difficult. If you post the script, or describe it, there might be a reason to use one or the other or none of the above. |
Hello ladies and gentlemen, I want to setup my own email server, on my home debian server. I am already running a website (have a FQDN), and static IP. There are numerous "simple" tutorials for setting up Dovecot, Postfix, and Squirrelmail. I will proceed cautiously. Was thinking of the following steps (more or less): 1. install Postfix and Dovecot 2. turn them both off -- until they are configured to my liking. 3. test them locally, before setting up MX and A records for the mail. My primary concern/question is: I don't want email spammers/frauder/etc, to send email from my domain before I can properly set it up. Should I be concerned about this? How can I subvert this? I am not a sys administrator, so I am doing this for the first time, and trying to be careful. | jalisco wrote: I want to setup my own email server, on my home debian server. I am already running a website (have a FQDN), and static IP. but then I am not a sys administrator, so I am doing this for the first time, and trying to be careful. Do you have a compelling reason why you want to do this? Mail server admin is, however private and/or low traffic it may be, something that requires your constant attention. You have to learn and keep up with any security issues and you will run into problems when delivering e-mail (you have a static IP, but maybe the world -- the blacklists -- thinks your IP is private and hence "spammy"), plus you will have to sign up for "feedback loops" with the dev^H^H^H Microsoft, Google, Yahoo and others. If you really really want to go ahead with this, first configure your firewall to block any access to any port opened by postfix and dovecot. This way you can play with them ON YOUR LOCAL SUBNET while the Internet is unaware of what you're doing. Luckily both dovecot and postfix have good (sane) defaults. But make sure your e-mail accounts have a good password (millions of bots will try to send e-mails (postfix sasl) and get your e-mails (dovecot)) plus something like fail2ban. Make a plan of what you want to have (spam and/or virus filtering, DKIM signing, DKIM validation, SPF, SPF policy, DMARC, DMARC policy, greylisting, etc. etc.) and prepare that (mind, paper) before you even apt install postfix. That should keep you busy for a while. Come back when you're ready :) Good luck. |
I can connect to eth0 but not wifi. My wifi router works as I can see my tablet is connected to it. I am not running this in a graphical environment. The system OS is Debian 9. Here is what I have: Code: Select all# ifconfig enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.103 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 2001:1970:4f9c:3600:9c13:4a7:bc2:ceec prefixlen 64 scopeid 0x0<global> inet6 fe80::3b79:848b:45c0:5df0 prefixlen 64 scopeid 0x20<link> inet6 2001:1970:4f9c:3600:f21f:afff:fe10:9efd prefixlen 128 scopeid 0x0<global> ether f0:1f:af:10:9e:fd txqueuelen 1000 (Ethernet) RX packets 4811072 bytes 7151090543 (6.6 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1502592 bytes 114259116 (108.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 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 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp2s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 6c:88:14:42:d1:f4 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Code: Select all#iwlist scan ... Channel:44 Frequency:5.22 GHz (Channel 44) Quality=70/70 Signal level=-36 dBm Encryption key:on ESSID:"C4BFBB756242-5G" Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=00000012ffb4e46a Extra: Last beacon: 2148ms ago IE: Unknown: 000F4334424642423735363234322D3547 IE: Unknown: 01088C129824B048606C IE: Unknown: 03012C IE: Unknown: 071E5553202401112801112C011130011195011E99011E9D011EA1011EA5011E IE: Unknown: 200103 IE: Unknown: 2D1AEF091BFFFFFF0000000000000000000100000000000000000000 IE: Unknown: 3D162C0D0000000000000000000000000000000000000000 IE: Unknown: 4A0E14000A002C01C800140005001900 IE: Unknown: 7F080100000000000040 IE: Unknown: BF0CB2018033EAFF0000EAFF0000 IE: Unknown: C005012A00FCFF IE: Unknown: C30402DEDEDE IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00 IE: Unknown: DD0900037F01010000FF7F IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: DD8D0050F204104A0001101044000102103B0001031047001003E16AE9D8A45A7494DE142899D168E010210013436973636F2053797374656D732C20496E632E10230007445043333834381024000744504333383438104200093030303030303030311054000800060050F2040001101100074450433338343810080002210C103C0001031049000600372A000120 Code: Select all# wpa_passphrase "dlink-DF50-5GHz" "blahblahpassword" > /etc/wpa_supplicant/wpa_supplicant.conf # cat /etc/wpa_supplicant/wpa_supplicant.conf network={ ssid="dlink-DF50-5GHz" #psk="mypasswordishere" psk=a588c892BLAHBLAHBLAHHHHHHHH4a49036467816f456cc7 } Code: Select all# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). auto enp7s0 allow-hotplug enp7s0 iface enp7s0 inet dchp auto lo iface lo inet loopback auto wlp2s0 iface wlp2s0 inet dhcp wpa-ssid "dlink-DF50-5GHz" wpa-psk "a588c89256dbBLAHHHHHHHHHHHHHHHHHHHHHa49036467816f456cc7" Code: Select all#ifup wlp2s0 ifup: /etc/network/interfaces:9: unknown or no method and no inherits keyword specified ifup: couldn't read interfaces file "/etc/network/interfaces" I had this working when I used just WEP mode on the modem, but it was slow (you could actually see the page slowly printing on the screen). As of now, the system boots and then stops for about 2 minutes trying to connect before it lets me in. I am then connected to enp0 (eth0). If I disconnected the network cord then enp0 disconnects but no wifi. Plugging back in brings enp0 up again. So hotplug is working, and the system appears to be reading the /etc/network/interfaces file. Any ideas? | /etc/network/interfaces Code: Select all# The loopback network interface auto lo iface lo inet loopback #Wifi auto wlan0 iface wlan0 inet dhcp wpa-ssid "my ISP router" wpa-psk "my password" That does it for me. BTW, did you install any non-free firmware necessary for your Wifi card? |
Hello everyone, I have just installed my little debian stretch system on my laptop (asus e406sa) but I'm having a lot of problems with this adapter (bluetooth/wifi) Qualcomm Atheros QCA9565 / AR9565 Now the wifi works fine but the bt module, when I try to use with blueman, doesn't work correctly. It appears "adapter not found", I have followed a lot of guides but I would need of your help to configure the bt module. Thanks! | Your wireless will work out of the box using the kernels ath9k driver. Your blutooth will require you to install firmware-atheros. https://packages.debian.org/stretch/firmware-atheros |
Not specifically a debian question, but I thought I would ask here, in case anyone knows. I have a email server running, and keep getting this in my mail.log. Jan 28 14:53:11 mail postfix/smtpd[25880]: connect from unknown[185.234.217.223] Jan 28 14:53:12 mail postfix/smtpd[25880]: lost connection after AUTH from unknown[185.234.217.223] Jan 28 14:53:12 mail postfix/smtpd[25880]: disconnect from unknown[185.234.217.223] ehlo=1 auth=0/1 commands=1/2 I have fail2ban installed, but it doesn't seem to be blocking this IP address, after repeated attempts. By repeated, I mean, constant, albeit slowly (maybe half a dozen per every ten minutes--spread across two IP addresses, from Ireland). Ring a bell for anyone? I will post a solution, if I find one sooner. | It has been so long since I last used fail2ban, so I don't remember exactly, but I do remember at first I thought it was not banning repeated attempts, so I looked at the manual;Code: Select allman fail2ban And I found there was a setting option that determines how many attempts before it is banned, the default was much higher then what I wanted, I changed it to ban on the 3rd attempt, and got good results. I think if you read the manual you will find the information you need, I don't have it handy now, because I am not using Debian or fail2ban, I know I could also search and get it online, but so can you, if you don't have it handy in your system. There also were plenty of details on configuring fail2ban available in the search results, when I had the same problem. I think there also are some threads here on the forum , but do remember clearly I never asked about it myself , here or any where, so maybe there are not any. ==== edited ==== If you showed more specific details on your configuration for fail2ban, some else might be able to see why or where ,and what you need to change. |
Hi All, I am trying to get a USB WiFi dongle to work with Debian Stretch (9.7). So far I have done the following: Identified the dongle using iwconfig / lsusb (see outputs below) Installed Realtek drivers (I added 'deb http://httpredir.debian.org/debian/ stretch main contrib non-free' to my /etc/apt/sources.list and installed firmware-realtek) Done a full update (update / upgrade / dist-upgrade) Setup /etc/network/interfaces with a static IP to connect to my WiFi Rebooted However, it is not working (I cannot get on the LAN using WiFi), and I am stuck, so looking for some suggestions. Further Info (Not sure if this helps): # iwconfig Code: Select allenp0s25 no wireless extensions. wlx000b8193b559 unassociated Nickname:"rtl_wifi" Mode:Auto Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 lo no wireless extensions. # lsusb Code: Select allBus 007 Device 002: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 003: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 0624:0200 Avocent Corp. Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub /etc/network/interfaces: Code: Select allauto lo iface lo inet loopback auto wlx000b8193b559 iface wlx000b8193b559 inet static address 192.168.1.105 netmask 255.255.255.0 gateway 192.168.1.254 wpa-ssid MyWiFiSSID wpa-psk MyWiFiPSK dns-nameservers 192.168.1.254 8.8.8.8 I removed the actual SSID and PSK, but everything else is a copy / paste. | Does this do anything: Code: Select all# ifup wlx000b8193b559 Is networking.service enabled? Check for enabled unit files with Code: Select allsystemctl list-unit-files --state=enabled |
I'm getting some weird behaviour from the bash completion feature. I configured quilt as is explained in the New Maintainers Guide [1], so this two lines are currently on my '~/.bashrc' file: Code: Select allalias dquilt="quilt --quiltrc=${HOME}/.quiltrc-dpkg" complete -F _quilt_completion -o filenames dquilt But it does not work as expected. I get: Code: Select all$ dquilt [Tab] $ dquilt bash: completion: function `_quilt_completion' not found quilt completion works fine: Code: Select all$ quilt [Tab] add edit grep mail previous revert top annotate files -h new push series unapplied applied fold header next refresh setup upgrade delete fork import patches remove shell diff graph init pop rename snapshot I made sure the function is actually called "_quilt_completion" by looking at the quilt completion file, '/usr/share/bash-completion/completions/quilt", has this lines: Code: Select all_quilt_completion() [...] _quilt_complete_opt="-o filenames" complete -F _quilt_completion $_quilt_complete_opt quilt unset -v _quilt_complete_opt So the function exists but it is somehow not finding it. But where it gets really weird is, if I run quilt and then the alias dquilt it works as expected for both: Code: Select all$ quilt [Tab] add edit grep mail previous revert top annotate files -h new push series unapplied applied fold header next refresh setup upgrade delete fork import patches remove shell diff graph init pop rename snapshot $ dquilt [Tab] add edit grep mail previous revert top annotate files -h new push series unapplied applied fold header next refresh setup upgrade delete fork import patches remove shell diff graph init pop rename snapshot What am I missing? Please help, you don't realize how useful is this autocompletion thing until it fails [1]: https://www.debian.org/doc/manuals/main ... ml#quiltrc -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages quilt depends on: ii bsdmainutils 11.1.2+b1 ii bzip2 1.0.6-9 ii diffstat 1.62-1 ii gettext 0.19.8.1-9 ii patch 2.7.6-3 ii perl 5.28.1-3 ii sensible-utils 0.0.12 Versions of packages quilt recommends: ii less 487-0.1+b1 Versions of packages quilt suggests: ii exim4-daemon-light [mail-transport-agent] 4.92~RC4-3 ii graphviz 2.40.1-5+b2 pn procmail <none> -- no debconf information | The completion works for me in buster. Have you created ~/.quiltrc-dpkg? |
Yesterday I followed this guide https://wiki.debian.org/SynapticsTouchp ... Stretch.22 and after I created /etc/X11/xorg.conf.d/40-libinput.conf with these lines Code: Select allSection "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "Tapping" "on" EndSection' the system, after reboot didn't start the x server. Practically after the command: Code: Select all$ systemctl restart lightdm I couldn't log in with graphical front end. Why? How can I activate the multitouch on my elantech? Thanks | Which error messages does the restart write? BTW: Try to look at this: wiki.Gentoo.org/wiki/Libinput#Troubleshooting. |
Hello I followed Head_on_a_Stick's post http://forums.debian.net/viewtopic.php?f=16&t=123694 and was able to set up non-graphical login everything works except auto login i created /etc/systemd/system/getty@tty1.service.d/override.conf with [Service] ExecStart= ExecStart=-/sbin/agetty --autologin <user name> --noclear %I $TERM replaced my username in the user name field but no go systemctl status getty@tty1.service gives below Failed to get properties: No such interface ls -lR /etc/systemd/system gives below /etc/systemd/system: total 36 lrwxrwxrwx 1 root root 53 Jan 13 06:46 dbus-org.freedesktop.nm-dispatcher.service -> /lib/systemd/system/NetworkManager-dispatcher.service lrwxrwxrwx 1 root root 37 Feb 5 23:06 default.target -> /lib/systemd/system/multi-user.target -rw-r--r-- 1 root root 412 Feb 5 21:40 display-manager.service drwxr-xr-x 2 root root 4096 Dec 28 23:07 getty.target.wants drwxr-xr-x 2 root root 4096 Feb 5 23:22 getty@tty1.service.d drwxr-xr-x 2 root root 4096 Jan 24 20:00 graphical.target.wants lrwxrwxrwx 1 root root 9 Feb 3 11:48 live-tools.service -> /dev/null drwxr-xr-x 2 root root 4096 Feb 3 11:02 multi-user.target.wants drwxr-xr-x 2 root root 4096 Dec 28 23:16 network-online.target.wants lrwxrwxrwx 1 root root 9 Jan 13 06:46 rtkit-daemon.service -> /dev/null drwxr-xr-x 2 root root 4096 Jan 25 12:06 sockets.target.wants drwxr-xr-x 2 root root 4096 Dec 28 23:19 sysinit.target.wants lrwxrwxrwx 1 root root 35 Jan 13 06:46 syslog.service -> /lib/systemd/system/rsyslog.service drwxr-xr-x 2 root root 4096 Dec 28 23:14 timers.target.wants /etc/systemd/system/getty.target.wants: total 0 lrwxrwxrwx 1 root root 34 Jan 13 06:46 getty@tty1.service -> /lib/systemd/system/getty@.service /etc/systemd/system/getty@tty1.service.d: total 4 -rw-r--r-- 1 root root 78 Feb 3 14:43 override.conf /etc/systemd/system/graphical.target.wants: total 0 lrwxrwxrwx 1 root root 43 Jan 24 20:00 accounts-daemon.service -> /lib/systemd/system/accounts-daemon.service /etc/systemd/system/multi-user.target.wants: total 0 lrwxrwxrwx 1 root root 35 Jan 13 06:46 anacron.service -> /lib/systemd/system/anacron.service lrwxrwxrwx 1 root root 42 Jan 23 15:50 binfmt-support.service -> /lib/systemd/system/binfmt-support.service lrwxrwxrwx 1 root root 37 Feb 3 11:02 cgmanager.service -> /lib/systemd/system/cgmanager.service lrwxrwxrwx 1 root root 35 Feb 3 11:02 cgproxy.service -> /lib/systemd/system/cgproxy.service lrwxrwxrwx 1 root root 44 Jan 28 17:39 clamav-freshclam.service -> /lib/systemd/system/clamav-freshclam.service lrwxrwxrwx 1 root root 41 Jan 13 06:46 console-setup.service -> /lib/systemd/system/console-setup.service lrwxrwxrwx 1 root root 32 Jan 13 06:46 cron.service -> /lib/systemd/system/cron.service lrwxrwxrwx 1 root root 38 Jan 13 06:46 irqbalance.service -> /lib/systemd/system/irqbalance.service lrwxrwxrwx 1 root root 38 Jan 28 18:01 live-tools.service -> /lib/systemd/system/live-tools.service lrwxrwxrwx 1 root root 38 Jan 15 18:38 lm-sensors.service -> /lib/systemd/system/lm-sensors.service lrwxrwxrwx 1 root root 38 Jan 13 06:46 networking.service -> /lib/systemd/system/networking.service lrwxrwxrwx 1 root root 42 Jan 13 06:46 NetworkManager.service -> /lib/systemd/system/NetworkManager.service lrwxrwxrwx 1 root root 36 Jan 13 06:46 remote-fs.target -> /lib/systemd/system/remote-fs.target lrwxrwxrwx 1 root root 33 Jan 13 06:46 rsync.service -> /lib/systemd/system/rsync.service lrwxrwxrwx 1 root root 35 Jan 13 06:46 rsyslog.service -> /lib/systemd/system/rsyslog.service lrwxrwxrwx 1 root root 31 Jan 20 18:34 ufw.service -> /lib/systemd/system/ufw.service lrwxrwxrwx 1 root root 47 Jan 13 06:46 unattended-upgrades.service -> /lib/systemd/system/unattended-upgrades.service /etc/systemd/system/network-online.target.wants: total 0 lrwxrwxrwx 1 root root 38 Jan 13 06:46 networking.service -> /lib/systemd/system/networking.service lrwxrwxrwx 1 root root 54 Jan 13 06:46 NetworkManager-wait-online.service -> /lib/systemd/system/NetworkManager-wait-online.service /etc/systemd/system/sockets.target.wants: total 0 lrwxrwxrwx 1 root root 32 Jan 13 06:46 uuidd.socket -> /lib/systemd/system/uuidd.socket /etc/systemd/system/sysinit.target.wants: total 0 lrwxrwxrwx 1 root root 42 Jan 13 06:46 keyboard-setup.service -> /lib/systemd/system/keyboard-setup.service lrwxrwxrwx 1 root root 45 Jan 13 06:46 systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service /etc/systemd/system/timers.target.wants: total 0 lrwxrwxrwx 1 root root 33 Jan 13 06:46 anacron.timer -> /lib/systemd/system/anacron.timer lrwxrwxrwx 1 root root 35 Jan 13 06:46 apt-daily.timer -> /lib/systemd/system/apt-daily.timer lrwxrwxrwx 1 root root 43 Jan 13 06:46 apt-daily-upgrade.timer -> /lib/systemd/system/apt-daily-upgrade.timer appreciate any help | sickpig wrote:replaced my username in the user name field Did you insert the chevrons around your username? If so then delete the chevrons, just the username should be entered with no other characters around it. EDIT: you are running systemd, right? Code: Select allcat /proc/1/comm EDIT2: check if the override is recognised with Code: Select allsystemctl cat getty@tty1 |
Hi everybody My mission is having the bootaa64.efi file working on my ARM64 Laptop (Asus Novago), which is able to boot others "bootaa64.efi" files. Today, Debian and Ubuntu versions does not boot (it freezes at running the EFI file). I successfully managed to build an ISO in a way that is identical to the official way, using https://salsa.debian.org/images-team/debian-cd and having a local mirror as needed. But it does not rebuild all the packages, it just put them together into a new ISO file. Also, with https://github.com/pbatard/uefi-simple I successfully managed to compile my own "aarch64.efi" file (for an ARM64 Laptop) and having it working on my ARM64 Laptop (it just shows a message and a "press any key" message in order to check if it works - and it works). On this ARM64 computer (Qualcomm Snapdragon 835 CPU) I'm also able to boot Windows and a working Windows installer. BUT : Linux distros EFI files do not boot (it freezes and does nothing) and I want to debug it, by building the EFI file myself, and customize code and target options in order understand what's not working (and may be find a solution). (Same problem for Ubuntu ARM64 and Debian ARM64) What is the way to do, the correct entry point, if I want to rebuild my own version of Debian Grub "bootaa64.efi" file ? I'm interested in doing this on the "Buster" version because Linux 4.18 and higher already contains all the necessary drivers for having Qualcomm functionnalities working out of the box with no kernel modifications Thanks in advance ! | The grub-efi package is only available for the x86 architectures, unfortunately. You could try systemd-boot, that provides /usr/lib/systemd/boot/efi/systemd-bootaa64.efi If that is copied to ${ESP}/efi/boot/bootaa64.efi then the UEFI firmware should boot it automatically.[1] The systemd-boot program looks for the configuration files defined on the ArchWiki page: https://wiki.archlinux.org/index.php/Systemd-boot I boot my (x86) Debian stable system this way, it works well EDIT: the kernel & initramfs need to be on the ESP for this to work, see https://wiki.debian.org/EFIStub for an example of a kernel post-install script that can automate this task. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.