You are not logged in.
Note that eth0 is being controlled by ifupdown rather than NetworkManager: https://wiki.debian.org/NetworkManager# … _Unmanaged
So try replacing "allow-hotplug eth0" with "auto eth0". Or use NetworkManager instead of ifupdown.
Don't bother with wicd, it's crap.
I'm on 5.4.0-0
Either switch to the non-backports kernel or build a new module from Larry Finger's github site.
The Ubuntu kernels are fixed now but the twats haven't passed it upstream. As usual.
Perhaps the key is sticking. Can you test with a different keyboard? Or perhaps try a live session to eliminate mis-configuration.
Are you running ntp or any other program that would synchronise your computer's clock from the internet? Sounds like perhaps your motherboard's CMOS battery is dead.
And anyway you shouldn't configure GNU/Linux to use a stupid time standard, configuring Windows to use a sane time standard is a *much* better approach:
Please open a new thread for this problem, thanks.
I am absolutely sure that the dnssec-trigger package from Devuan does not set /etc/resolv.conf immutable so please include details of how you installed it and also the full output of apt policy in the new OP.
Did the wizard ask you which modifier to use? I just tried it myself and it asked me.
The relevant section in ~/.config/i3/config seems to be
set $mod Mod4Do you have that?
but the dnssec-trigger package comes from nlnet labs, and they would
Well I've just tried installing the dnssec-trigger package in the Devuan ASCII live environment and it did not set resolv.conf immutable, I was able to alter and delete the file afterwards with the usual root permissions.
Try
i3-config-wizard^ That should ask which modifier key to use as the default.
Remove your extant configuration file beforehand though to prevent conflicts. You can re-apply your options to ~/.config/i3/config afterwards.
If you decide to go with a conventional installation to the USB stick:
I know I'm probably not going to have full disc encryption
It is possible to have full disk encryption with /boot included: https://bugs.debian.org/cgi-bin/bugrepo … =814798#15
To have a system that is bootable from both UEFI & non-UEFI machines use a GUID partition table (GPT) and include a BIOS boot partition[1] as well as an EFI system partition (ESP)[2] then install in non-UEFI mode, boot the system and run
# apt install grub-efi-{amd64,ia32}-bin
# mount /dev/sdXY /mnt
# grub-install --target=x86_64-efi --efi-directory=/mnt --removable
# grub-install --target=i386-efi --efi-directory=/mnt --removable^ That will install the 32- & 64-bit UEFI versions of GRUB and allow booting in both modes (replace X & Y with the drive letter & partition number assigned to the ESP).
There is a chance that some very old machines won't boot from a GUID partition table but I think the above method gives the best chance of universality.
[1] Apply the "bios_grub" flag in gparted or type "EF02" in gdisk, it should have no filesystem, I prefer to use sectors 34-2047 which should be free in a correctly aligned disk.
[2] Apply the "boot,esp" flag in gparted or type "EF00" in gdisk, it should be FAT-formatted, I prefer to use 512MiB but ~100MiB should be plenty.
Tried that and got 'command not found' so I guess those fonts are not installed?
They're not fonts, the package is for configuration of the fontconfig package.
So try
# apt install fontconfig fontconfig-config
# dpkg-reconfigure fontconfig fontconfig-configYou may even find that the hinting options start making a difference afterwards.
They are awesome, thanks for sharing!
I followed this
No you didn't. That guide advises to create a new file at /etc/X11/xorg.conf.d/40-libinput.conf with the suggested content. But you need to run the commands as root for them to work.
Or with sudo:
sudo mkdir -p /etc/X11/xorg.conf.d
sudo tee /etc/X11/xorg.conf.d/40-libinput.conf <<END
Section "InputClass"
Identifier "libinput touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
Option "Tapping" "on"
EndSection
ENDYou've added your configuration to the pointer section rather than the touchpad section, which is why it doesn't work. And using /usr/share/X11/xorg.conf.d/40-libinput.conf means your changes will be over-written if the xserver-xorg-input-libinput package is upgraded.
No, I didn't even know the immutable attribute existed until I figured out how to remove it. Something else set it
You must have blindly copy&pasted some forum suggestion, no De??an package would use such an awful hack.
The real problem is that dnssec-trigger doesn't work anymore. DNS info is not looked up and the machine cannot use the network with it installed. Something in the batch of updates I downloaded broke it.
You should probably open a new thread for that problem, dnssec-trigger & unbound should work just fine.
Autologin is a function of the display manager (SLiM) rather than the desktop environment.
So edit /etc/slim.conf and edit these two lines:
default_user username
auto_login yesReplace username with your actual username.
Debian buster doesn't use SLiM (because it's dead upstream and it won't support systemd login sessions correctly), see https://wiki.debian.org/LightDM#Enable_autologin for the required LightDM configuration. Or better yet remove LightDM (it runs X as root, which is bad) and follow http://forums.debian.net/viewtopic.php?f=16&t=123694 instead.
Sorry for the trouble, I presumed you had tested the new kernel before attempting to remove the old versions.
Use apt to re-install the old kernel versions:
cd /var/cache/apt/archives
sudo apt install ./name_of_old_kernel_version.deb^ That will downgrade automatically.
it was a completely different file control system than chmod, something I've never heard of before "chattr"
You did that yourself, Devuan ASCII doesn't have dnssec-trigger installed by default and /etc/resolv.conf is not set immutable.
If you use TrueType fonts then try
# dpkg-reconfigure fontconfig-configAnd change the font tuning method to "Autohinter".
Otherwise navigate to Applications Menu → Settings → Appearance → Fonts and play with the hinting method. MX use "slight" hinting.
It's probably also worth noting that MX-19 is based on Debian buster and so has a newer version of fontconfig. Have you tried the Refracta beta image? That uses a beowulf base with the same fontconfig version as MX-19 (but it has hinting set to "none" in the stock desktop).
Sorry Micronaut, my dyslexia is playing up again — I read "4.9" as "4.19", you have the correct kernel version for ASCII.
For your networking problem check the output of rfkill, there have been a couple of threads involving that recently.
I think you have the proposed-updates repository enabled, are you sure that's what you want? Those packages can be buggy.
Devuan beowulf's current ABI is 4.19.0-8: https://pkginfo.devuan.org/stage/beowul … b10u3.html
You have a metapackage (linux-image-amd64, to keep the kernel updated) and four different ABI versions.
Run
# aptitude purge linux-image-4.9.0-{6,9,11}-amd64To get rid of the old ABI versions.
See also https://kernel-team.pages.debian.net/ke … sions.html
EDIT: better link.
EDIT2: I can't count...
The Debian instructions on their site should work, either download and install the .deb package or add their repositories. The former option is probably "safer" because you're not relying on their repositories being well-maintained but the second option ensures automatic updates.
Can you tell me how to do it
Just add your rfkill command on a single line at the end of the file at /etc/rc.local
no
So try
# rfkill unblock allGood.
You can add the rfkill command to /etc/rc.local to get it to run automatically on boot. Or make a custom service to run it if you want more control.
Obviously I already tried
~# rfkill unblock alland this worked too, but I have to do it every time I turn on my laptop... Super annoynig.
What is the status of the rfkill kernel module?
cat /sys/module/rfkill/parameters/default_stateIt should be "1", if it's "0" then change that by creating a file at /etc/modprobe.d/rfkill.conf with this content:
options rfkill default_state=1