You are not logged in.
What is your video card? You probably just need some firmware. The Debian wiki has a page on the subject which may be applicable here.
Hope to elicit some "how to" clarification
sudo apt update && sudo apt upgradeSay "yes" when it asks if you want to change the release.
#!/bin/sh
_uptime=$(uptime|cut -c 2-19)
_rsync_status=$(/etc/init.d/rsyncd status) # does not need root!
_memavail=$(grep -i memavailable /proc/meminfo) # save those poor cats!
_memfree=$(grep -i memfree /proc/meminfo) # ditto
_fs_status=$(df -h|awk '!/^Filesystem/&&!/\/dev\/root/&&!/tmpfs/{ print $5 " " $1}') # awk can search so no need for grep
_drive_temp=$(sudo smartctl -d ata -A /dev/sda | grep Temperature | cut -c 5-8,87-89)
printf '%s\t\t%s\n\n' "uptime:" "$_uptime" # \t adds tab characters, \n adds new lines, %s defines strings which are listed afterwards
printf '%s\t%s\n\n' "rsync daemon status:" "$_rsync_status"
printf '%s\n%s\n%s\n\n' "memory status:" "$_memavail" "$_memfree"
printf '%s\t%s\n\n' "filesystem status:" "$_fs_status" # might not work :/
printf '%s\t%s\n' "drive temperature" "$_drive_temp"I'm trapped in Windows atm so this is untested, I'll post back later when I'm in a proper OS...
EDIT: fixes...
I use iPhone tethering for my network conections so I have, and to try and get around the time and date settings being incorrect I have removed ntp-client/server.
Can you explain further why you had to remove ntp? If your motherboard CMOS battery is dead or dying then you will need ntp to set the time correctly at boot.
Which kernel version was Void on?
I did not want to create a symbolic link, I installed usrmerge
The usrmerge package works by creating symlinks; check ls -l /bin/mount.
Has this problem been reported to Debian as a bug?
So I presume the firmware-amd-graphics package is installed? I don't think the desktop would start if it wasn't.
Check the machine firmware ("BIOS") options for anything relating to sleep functions — my ThinkPad P14s needs to be changed from "Windows" to "Linux" in the sleep mode section to resume properly under the latter.
@OP: try
# apt purge live-boot-initramfs-tools open-infrastructure-system-boot^ Those packages provide that hook and should not be installed except in the live environment.
So you have a working login session but the machine won't resume. What is your graphics hardware and driver?
lspci -knn | grep -iA3 'vga\|3d\|display'Bonjour PengouinPdt, ça va?
live-boot: core filesystems dm-verityE: /usr/share/initramfs-tools/hooks/live failed with return 1.
From where did you obtain that hook? It shouldn't be present in an installed system.
Here are the standard hooks: https://salsa.debian.org/kernel-team/in … ster/hooks
And for future reference my French is (almost) passable but you can make the terminal commands speak English by putting LC_ALL=C before the command.
Find out what is providing the service supervision and query that utility using the provided tools. This is completely off-topic for these boards so I won't go any further here. I refer you again to the OpenWRT forums. I don't mean to be rude but your continued posting of OpenWRT-related issues on these boards is starting to look like spam.
Now, in my Devuan box, I can find service:
[root@devuan ~]# which service /usr/sbin/service [root@devuan ~]#But not in my NAS:
root@OpenWrt:~# which service root@OpenWrt:~#
The which command searches PATH for the named executable.
Run this command in your Devuan system:
echo $PATH^ That will show a (colon-separated) list of the directories being searched. If you run that command from OpenWRT then it will probably not have /usr/sbin/ listed, hence which cannot find it.
That being the case you need to either add /usr/sbin/ to PATH or declare the full path when running executables from that directory.
See https://wiki.debian.org/EnvironmentVariables for the Debian documentation on setting PATH and if that doesn't work then ask on the OpenWRT forums instead.
root@OpenWrt:~# /usr/bin/service -ash: /usr/bin/service: not found root@OpenWrt:~#
Did you not think to try
/usr/sbin/service rsyncd status@OP: have you considered using unattended-upgrades instead? Hands-free updating should be "safe" for the stable release and ensures timely security fixes.
Is cassowary in sys.path? Read the warning in your linked guide.
Perhaps try
PYTHONPATH=/path/to/cassowary python3 -m cassowary -aBut I'm not using pip to test this. It's *much* better to package Python modules properly IMO.
Please post the output of
loginctl session-status
pgrep -a logindDoes this suspend your machine:
doas tee /sys/power/state <<<"mem"Sorry, that should have been
# apt install --target-release beowulf-backports rsync libzstdManually running it as root doesn't work:
/media/cdrom/auotrun.sh returns "permission denied"
The file needs to be made executable (chmod +x) before it can be run directly.
Use apt install --target beowulf-backports rsync libzstd. The /beowulf-backports incantation doesn't allow for dependencies to be installed from backports.
I think aptitude might be able to figure out the path to installation with the /release syntax where dependencies are involved.
https://dev1galaxy.org/viewtopic.php?id=4483
Please search the boards before posting...
Excuse me if I am being ignorant. But pipewire also can deal with video?
Isn't this the kind of encroachment systemd is guilty of? Doing too much?
Yeah, sure, why not.
And hey, it does Bluetooth now as well:
https://www.collabora.com/news-and-blog … pdate.html
Stonks!
Version 7.1 of oksh is now building and should be available soon.
Have you tried installing gnome-packagekit again? It didn't break the live system so this problem seems peculiar to your machine rather than Devuan itself.
if I should ever want to try something from backports, it's already listed there, so all I would have to do is uncomment it temporarily
If you install backported packages the repository should be left enabled so that the package(s) can be updated from there.
It would appear that gnome-packagekit is likely the reason why my earlier installation of package-update-indicator caused a problem in Synaptic
Please confirm that by installing gnome-packagekit in your now functional system. As I said that package does not break Synaptic in the live environment.
@OP: what did you install from experimental?
aptitude search '?narrow(?installed, ?archive(experimental))'I've just installed package-update-indicator (and gnome-packagekit) in a Devuan chimaera live ISO environment and Synaptic works just fine afterwards.
Version 7.1 of loksh is now building and should be available soon.
Sorry for the delay, I was waiting for ibara@ to update their version but it looks like they're busy atm.