You are not logged in.
Maybe there's a problem with the edit you made to 90-alsa-restore.rules. I think "append" is not the right thing to do. There's a one-line replacement needed. It should look like the following.
Note: If you don't want it to be overwritten on update, put it in /etc/udev/rules.d instead of /usr/lib/udev/rules.d.
# do not edit this file, it will be overwritten on update
ACTION=="add", SUBSYSTEM=="sound", KERNEL=="controlC*", KERNELS!="card*", TEST=="/usr/sbin", TEST=="/usr/share/alsa", GOTO="alsa_restore_go"
GOTO="alsa_restore_end"
LABEL="alsa_restore_go"
ENV{ALSA_CARD_NUMBER}="$attr{device/number}"
# mark HDA analog card; HDMI/DP card does not have capture devices
DRIVERS=="snd_hda_intel", TEST=="device/pcmC$env{ALSA_CARD_NUMBER}D0p", RUN+="/bin/sh -c 'echo ALSA_CARD_HDA_ANALOG=$env{ALSA_CARD_NUMBER} >> /run/udev/alsa-hda-analog-card'"
# check for ACP hardware
TEST=="device/device/acp3x-dmic-capture", GOTO="alsa_hda_analog"
TEST=="device/device/acp6x-dmic-capture", GOTO="alsa_hda_analog"
TEST=="device/device/acp63-dmic-capture", GOTO="alsa_hda_analog"
TEST=="device/device/acp-dmic-codec", GOTO="alsa_hda_analog"
GOTO="alsa_restore_std"
LABEL="alsa_hda_analog"
# restore configuration for profile with combined cards (HDA + digital mic)
TEST!="/run/udev/alsa-hda-analog-card", GOTO="alsa_restore_std"
IMPORT{program}="/usr/bin/cat /run/udev/alsa-hda-analog-card"
ENV{ALSA_CARD_HDA_ANALOG}!="", ENV{ALSA_CARD_NUMBER}="$env{ALSA_CARD_HDA_ANALOG}"
LABEL="alsa_restore_std"
TEST!="/etc/alsa/state-daemon.conf", TEST=="/usr/sbin/alsactl", RUN+="/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore $env{ALSA_CARD_NUMBER}"
TEST=="/etc/alsa/state-daemon.conf", TEST=="/usr/sbin/alsactl", RUN+="/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime nrestore $env{ALSA_CARD_NUMBER}"
LABEL="alsa_restore_end"It should be "root=/dev/userr-vg-root" in the boot command. Check to make sure /etc/crypttab and /etc/fstab are correct. Also might be helpful to boot a live-usb and try opening and mounting the root partition manually just to make sure that part works.
I got that yesterday on a youtu.be link. After going through several screens of bicycles and busses (and clicking on every box that did NOT have what they asked me to identify) I clicked on boxes to form letters, one for each screen. Total of 7 letters, two words, to tell them how I felt about it.
Then I switched from firefox-esr to tor-browser and got right to the page I wanted.
I think it's simpler than that. Hardware is hard - you could drop it on your foot. The bits and bytes are not hard, so they are called soft.
Using a non-standard port for ssh (or any service) doesn't work as well as it used to. If your server is exposed to the internet, it's just a matter of checking your IP address to see what ports you have open.
Search here: https://search.censys.io/
Running a single app as root is useful and sometime necessary. Running the entire desktop as root can be unnecessarily risky if you're online or if someone else could sit down at your station and use your computer.
Main menu:
Applications -> Settings -> Removable Drives and Media
Then check appropriate boxes.
Thunar file manager:
Devices should show up in the left side panel. I don't recall if I had to change any settings to get that. That would either be in Edit -> Preferences or View.
@Mercury: Thanks for that snippet. Now I can get it to work with loginctl.
One odd thing I noticed - after testing it a couple times with loginctl, it no longer worked with pm-hibernate until after I rebooted.
It's linux. There are 10 ways to do anything. Pick one.
If you have a root account, you can su to root to do admin tasks. If you don't have a root account, you need to use sudo to do admin tasks, and in that case, you're probably a member of the sudo group and can do anything with it.
The original intent of sudo was to allow fine-grained permissions for certain users or groups to do a few specific admin tasks rather than give them total root access.
What you should not do is log into a desktop session as root.
Yeah, I have sudo NOPASSWD set for a few commands for one user. That's all.
What is says is that if you want to use sudo to run a command in /usr/local/(s)bin, you must now give the full path to the command.
What I see is that I do not have to give the full path to run the command with sudo, but maybe that's because I have the full path to the command already in my /etc/sudoers.d/usercommands. So for me, there's no change. Tested this in freia with the version of sudo mentioned above.
Thanks. I got it to work with pm-hibernate. I put a simple script in /etc/sleep.d/testmessage and it ran. Just this...
#!/usr/bin/env bash
echo "$(date)" > /home/user/TESTMESSAGE
exit 0If I want to run a script when resuming from hibernation, google tells me to do something with systemd. That's not an option. I poked around in /etc/acpi/ and /etc/elogind/ and I can't figure it out. I did read a few man pages, too. It's probably not difficult, but requires knowing where/what to tweak.
apt install network-manager" This package provides the userspace daemons and a command line interface to
interact with NetworkManager."
Do not install network-manager-gnome or network-manager-applet.
$ apt-file list network-manager | grep bin
network-manager: /usr/bin/nm-online
network-manager: /usr/bin/nmcli
network-manager: /usr/bin/nmtui
network-manager: /usr/bin/nmtui-connect
network-manager: /usr/bin/nmtui-edit
network-manager: /usr/bin/nmtui-hostname
network-manager: /usr/sbin/NetworkManagerConfirmed.
task-lxqt-desktop and sddm are installed, but there are no lxqt packages installed. Boots to console login. And 'startx' seems to be missing, although there are xorg packages installed.
I've installed lxqt in freia a few times previously, but always after a base (no-X) install. This is the first time I've tried selecting lxqt from the tasksel menu, so I don't know if this is a new behavior or not.
apt install lxqt brings in a lot. (Total 1477 packages) It looks like everything is there now.
@RecklessEpoch: Sometimes if you continue past that first note about adding the missing firmware from removable media, you can still set up the wireless when the installer gets to the network setup. The firmware is in that iso. Did you try that, or just bail out of the installer when you got that message?
@greenjeans: I recommend eye protection, or at least cover the knife with your free hand when you cut it. I once had a habanero seed fly up into my eye. Not fun. And be careful where you put your fingers afterward.
That's weird. I'm not seeing that in my turnstile iso. If I remove turnstile, it does not want to remove anything else. If I try to remove dbus, it wants to remove audacious along with another 85 packages.
Make sure you get rid of all the pipewire, wireplumber and pulseaudio packages, and then alsa should work. (libpulse0 can stay and won't interfere.) Make sure you're using the right sound card. 'aplay -l' will show you which one is card 0 and if there's more than one, such as hdmi from your cpu, it'll show which one is card 1. There are a few ways to set the system to use the right card. Ask if you need help with that.
This one does not have elogind or consolekit or turnstile. Just seatd and some elogind libraries. No display manager. I think you could remove some of those libraries if you removed the lxqt packages.
https://get.refracta.org/files/experime … 4_1517.iso
The turnstile iso has turnstile for user services. It's only used for pipewire in the iso you used. Turnstile uses the script in ~/.user_session.d
Did you revert to using only alsa for audio after removing turnstile?
I gave a link to this discussion to our webmaster and we can add the information to the guide. I also made a note in my TODO list for refractainstaller. Thanks!
Booting a usb in uefi mode varies depending on the motherboard. I usually bring up the boot device menu to boot from usb, and some motherboards give a choice of booting it either way. The devuan-live isos when imaged to a usb stick (using dd or cat) should boot whichever way the bios is set to boot the hard disk, but that doesn't always work out. Again, that depends on how the motherboard implements uefi (i.e. how it deviates from standards.)
A simpler way to install to the removable media path is to edit /etc/refractainstaller.conf to uncomment the media_opt line.
# UEFI Removable Media Path
# Uncomment to force installation to the removable media path also.
# This option is only available on EFI.
# Default is commented out.
#media_opt="--force-extra-removable"Maybe it will work better like this:
apt install nvidia-driver=535.309.01-0+deb12u1 nvidia-kernel-dkms=535.309.01-0+deb12u1It's easier with freia. You don't need backports. I'm looking at my freia now and a few packages are newer than what I posted in July. I think the instructions for the sources say to use "testing". Follow NexuSfan's instructions.
runit uses the sysvinit script if there is no runit script for a service. Install the runit-services package to get some run scripts.
Installing yt-dlp from the repo is pointless since every version stops working after a short time due to youtube's efforts to stop yt-dlp from working. That's probably why the maintainer doesn't bother to update it.
This page has some helpful information -
https://vidkraken.com/blog/yt-dlp-403-forbidden