Posts by migf

migf · Hardware & System Configuration

Great, many thanks: it works!

There were small changes in the /etc/network/interfaces, for instance no equal signs between options and their values, that I think are just for making people like me to be confused.

Marking this thread as solved, and many thanks again!

migf · Hardware & System Configuration

What is the content of wpa_supplicant.conf? How did you generate it?

I generated it as I did for previous laptops: using wpa_passphrase to encode the key. Its contents are:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

network={
  ssid="XXX"
  scan_ssid=1
  key_mgmt=WPA-PSK
  psk=.......
}

Has this been deprecated?

migf · Hardware & System Configuration

@rolfie: Thanks for your tip!

There has been some progress: using eth0 I could upgrade and update the system, with a new kernel version, 5.19, and the Realtek firmware of the version I sought:

[    3.868460] rtw89_8852ae 0000:01:00.0: enabling device (0000 -> 0003)
[    3.871490] rtw89_8852ae 0000:01:00.0: firmware: direct-loading firmware rtw89/rtw8852a_fw.bin
[    3.871504] rtw89_8852ae 0000:01:00.0: Firmware version 0.13.36.0, cmd version 0, type 1
[    3.871506] rtw89_8852ae 0000:01:00.0: Firmware version 0.13.36.0, cmd version 0, type 3
[    3.888028] rtw89_8852ae 0000:01:00.0: chip rfe_type is 1

However, with ifdown eth0 and ifup wlan0 the latter hangs and must be backgrounded. The kernel messages show also that some features are disabled:

[   66.744949] r8169 0000:02:00.0 eth0: Link is Down
[   79.935440] wlan0: authenticate with ec:1a:59:88:2f:25
[   79.935455] wlan0: bad VHT capabilities, disabling VHT
[   79.935457] wlan0: Invalid HE elem, Disable HE
[   80.158538] wlan0: send auth to ec:1a:59:88:2f:25 (try 1/3)
[   80.160026] wlan0: authenticated
[   80.160231] rtw89_8852ae 0000:01:00.0 wlan0: disabling HT/VHT/HE as WMM/QoS is not supported by the AP
[   80.162542] wlan0: associate with ec:1a:59:88:2f:25 (try 1/3)
[   80.165039] wlan0: RX AssocResp from ec:1a:59:88:2f:25 (capab=0x411 status=0 aid=1)
[   80.278693] wlan0: associated
[   80.350754] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Then no nameserver is seen with a Network unreachable error. So it seems that this command did not finish the network configuration. Moreover trying to turn off the interface also hangs and must be interrupted:

# ifdown wlan0
ifdown: waiting for lock on /run/network/ifstate.wlan0
^CGot signal Interrupt, terminating...
^C
#

The relevant lines of /etc/network/interfaces are

allow-hotplug eth0
iface eth0 inet dhcp

iface wlan0 inet dhcp
    pre-up wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0

and here are the contents of /etc/resolv.conf

domain XXX
search XXX
nameserver 192.168.2.1

Is there any way of configuring manually the network, apart from adding IPs and hosts to /etc/hosts?

migf · Hardware & System Configuration

I am stuck again, now with a Temporary failure resolving 'deb.devuan.org' error when trying apt update.

I already read the https://dev1galaxy.org/viewtopic.php?id=5133 thread in this forum, and following a tip there I changed my router
DNS settings to point to OpenDNS. This solved the problem in my desktop, but not in the laptop.

I noticed that dig deb.devuan.org

gets 125.228.189.120 with a warning recursion requested but not available[
with the -4 option starts with the warning Message parser reports malformed message packet but the rest is identical
with -6 it just freezes

host debuan.dev.org works fine with no option or with -4, but freezes with -6. So maybe this a problem of something trying to use ipV6 at some stage.

I also tried to use the mirror repo.ifca.es/devuan-cd by editing the apt sources list, but the results are similar.

I do not know if there is any relation with problems of Firefox that cannot access any web server. This may result from the avahi-daemon not being installed: I get rid of it because it created an interface etho:avahi that could not be controlled by ifup and ifdown, and that used some strange IP (not in the LAN).

migf · Hardware & System Configuration

Ceres now has the firmware from 2022-10-18 so you can use that.

Thanks a lot for your reply! I was not aware of the Ceres release, but if it is based on Debian unstable I could not find that version there some days ago.

I will try this tomorrow and will report back.

migf · Hardware & System Configuration

In a previous thread https://dev1galaxy.org/viewtopic.php?id=5300 I got very nice advice on how to install firmware for the Realtek wireless from the backports repositories, and this apparently solved the problems I was having. Some days later I found out that although the device was then seen the connection was unstable and is unusable: dmesg was full of messages like this:

rtw89_pci 0000:03:00.0:  [FWBB][WARN][CMW] No specific sta connect

A lengthy search led me to this thread in kernel.org https://lkml.kernel.org/linux-wireless/ … tek.com/T/ that
advises the use of some options to the Realtek kernel modules (rtw89_core, rtw89_pci), and the use of the firmware version 0.13.36.0, while the latest one in Debian bullseye is 0.9.12.2.

So I got the bin file from https://git.kernel.org/pub/scm/linux/ke … mware.git/ and I am now trying to find out what to do with it,
as I am confused with all the methods I found out in the net for upgrading firmware...

Is that enough to put the file in /lib/firmware/rtw89/ as in that thread, or is this unsafe? If unsafe what is the recommended method? The laptop is a HP with UEFI boot.

Thanks in advance for any help.

migf · Hardware & System Configuration

The same would be true for the header files as well.

Ok, done! Thanks again to both!

I will now mark this as solved.

migf · Hardware & System Configuration

@Head_on_a_Stick

Thanks for your tip: I have now the backported metapackage.

migf · Hardware & System Configuration

OK, that is it! wlan0 is now available and working, thanks a lot.

If I may put a related question: I am getting this in dmesg concerning the firmware of the Radeon GPU:

 [drm:amdgpu_pci_probe [amdgpu]] *ERROR* amdgpu requires firmware installed
[    3.067618] amdgpu: See https://wiki.debian.org/Firmware for information about missing firmware

Is there also a package for it, and is it recommended to add this firmware?

Thanks again!

migf · Hardware & System Configuration

Thank you very much for both replies!

I added the backports line to the apt sources.list and I just found out I missed "non-free" there, but I think this will not change what I describe below.

@Head_on_a_stick: I found out that linux-image-amd64 was already there and when I tried to reinstall it apt answered that the 5.10 kernel would be installed; so
I quit.

@nixer: I tried to install linux-image-5.18.0-0 as you suggested but there are several packages that match this name:

# apt-get install -t chimaera-backports linux-image-5.18.0-0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'linux-image-5.18.0-0.deb11.4-rt-amd64-dbg' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-amd64-unsigned' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-amd64' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-amd64-dbg' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-cloud-amd64' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-cloud-amd64-dbg' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-rt-amd64-unsigned' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-rt-amd64' for regex 'linux-image-5.18.0-0'
Note, selecting 'linux-image-5.18.0-0.deb11.4-cloud-amd64-unsigned' for regex 'linux-image-5.18.0-0'
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:
 linux-image-5.18.0-0.deb11.4-amd64 : Conflicts: linux-image-5.18.0-0.deb11.4-amd64-unsigned but 5.18.16-1~bpo11+1 is to be installed
 linux-image-5.18.0-0.deb11.4-amd64-unsigned : Conflicts: linux-image-5.18.0-0.deb11.4-amd64 but 5.18.16-1~bpo11+1 is to be installed
 linux-image-5.18.0-0.deb11.4-cloud-amd64 : Conflicts: linux-image-5.18.0-0.deb11.4-cloud-amd64-unsigned but 5.18.16-1~bpo11+1 is to be installed
 linux-image-5.18.0-0.deb11.4-cloud-amd64-unsigned : Conflicts: linux-image-5.18.0-0.deb11.4-cloud-amd64 but 5.18.16-1~bpo11+1 is to be installed
 linux-image-5.18.0-0.deb11.4-rt-amd64 : Conflicts: linux-image-5.18.0-0.deb11.4-rt-amd64-unsigned but 5.18.16-1~bpo11+1 is to be installed
 linux-image-5.18.0-0.deb11.4-rt-amd64-unsigned : Conflicts: linux-image-5.18.0-0.deb11.4-rt-amd64 but 5.18.16-1~bpo11+1 is to be installed
E: Unable to correct problems, you have held broken packages.

What is the one to be selected?

migf · Hardware & System Configuration

I have installed Chimaera on a recent HP having a Realtek8852 wireless chipset whose firmware is missing.

I already tried some solution I found out in the Debian site, the result being that I had to reinstall everything from scratch,
and I am aware of the driver in [https://www.amd.com/en/support/graphics/radeon-rx-vega-series/radeon-rx-vega-series/radeon-rx-vega-64] that seems to still have issues.

So I think there may be two more easier solutions

install a more recent kernell like 5.18 and stop using the one in the Chimaera distribution: will this solve the problem, and is it a safe solutiom?
keep the current kernel and buy a dongle that is known to work with it: what such dongles are there?

I will be very grateful for any help on this!

migf · Installation

Thanks for your suggestions: unhappily I followed them and things stay as before.

I think that the grub error may just mean that no saved state was found in the swap area.

As to the permissions to use pm-suspend and others, this was probably already solved because the options for suspending and hibernating are now available in the logout actions that slim presents. Moreover I have also been trying to suspend as root and the result is the same.

Just for the record I made an apt-get update and dist-upgrade as it could be there were some new things missing but nothing came of it,

migf · Installation

By using blkid --fs I found out that the swap uuid, then edited /etc/default/grub to change the GRUB_CMDLINE_LINUX_DEFAULT:

GRUB_CMDLINE_LINUX_DEFAULT="resume=7ade7026-f504-4f6e-a768-105e4a93b05e quiet"

After a suspend and hard reset, GRUB complained "Invalid resume device". A new suspend behaved as before,

I found out this Gentoo page https://wiki.gentoo.org/wiki/Suspend_and_hibernate but I am not sure if anything there is what is needed in Devuan. I tried

cat /sys/power/state
 freeze mem disk

I don't know if this output is the one to be expected.

migf · Installation

fsmithred wrote:
I ran fsck from another system on the same machine and it fixed some orphaned inodes.
...
Have you tried running loginctl suspend to see if it acts differently?

The hard resets I have made after suspends being blocked led to disk journals being recovered but no other problems. So I thought there was no need for
fsck's: am I wrong?

I tried loginctl suspend and the behaviour is the same of using the other methods.

Marjorie wrote:
Have you specified the swap partition where you are saving the hibernation image?
If the system is hibernating and you really just want it to suspend then you need to track down where PM is making the 'wrong' call.

My grub.cfg has no such field (neither before nor after the upgrade). I will try and add one tomorrow morning first thing and will report.

In fact the syslog has a lot of entries about hibernation but I am sure I am asking for a suspend not a hibernation. As I wrote in a previous post this
behaviour happens also with the command pm-suspend.

migf · Installation

I was replying and was logged out... So I will restart and will be brief.

Ok to staying in this thread.

This is a desktop, I used the keyboard to awake a suspend.

I had saved pm-suspend.logs from before and after the upgrade. The main difference between them is that the 2nd entry below is now missing (the error in the 3rd appears in both) and there is no awake:

Running hook /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend:
/usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/55wicd suspend suspend:
/usr/lib/pm-utils/sleep.d/55wicd suspend suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend:
Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
/usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: success.

What appears after the PM entries in the syslogs are completely different and I cannot make out what the problem is. So I post them below.

Before the upgrade:

Mar 14 14:06:13 khashkol kernel: [15740.516318] PM: suspend entry (deep)
Mar 14 14:37:52 khashkol rtkit-daemon[3171]: The canary thread is apparently starving. Taking action.
Mar 14 14:37:52 khashkol rtkit-daemon[3171]: Demoting known real-time threads.
Mar 14 14:37:52 khashkol kernel: [15740.516321] PM: Syncing filesystems ... done.
Mar 14 14:37:52 khashkol kernel: [15740.741424] Freezing user space processes ... (elapsed 0.001 seconds) done.
Mar 14 14:37:52 khashkol kernel: [15740.742981] OOM killer disabled.
Mar 14 14:37:52 khashkol kernel: [15740.742982] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Mar 14 14:37:52 khashkol kernel: [15740.744216] Suspending console(s) (use no_console_suspend to debug)
Mar 14 14:37:52 khashkol kernel: [15740.764435] sd 1:0:0:0: [sda] Synchronizing SCSI cache
Mar 14 14:37:52 khashkol kernel: [15740.764446] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Mar 14 14:37:52 khashkol kernel: [15740.764450] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
Mar 14 14:37:52 khashkol kernel: [15740.764556] sd 3:0:0:0: [sdb] Stopping disk
Mar 14 14:37:52 khashkol kernel: [15740.764600] sd 5:0:0:0: [sdc] Stopping disk
Mar 14 14:37:52 khashkol kernel: [15740.764602] sd 1:0:0:0: [sda] Stopping disk
Mar 14 14:37:52 khashkol kernel: [15745.596679] ACPI: Preparing to enter system sleep state S3
Mar 14 14:37:52 khashkol kernel: [15745.597589] PM: Saving platform NVS memory
Mar 14 14:37:52 khashkol kernel: [15745.597751] Disabling non-boot CPUs ...
Mar 14 14:37:52 khashkol kernel: [15745.613549] smpboot: CPU 1 is now offline
Mar 14 14:37:52 khashkol kernel: [15745.630250] smpboot: CPU 2 is now offline
Mar 14 14:37:52 khashkol kernel: [15745.645691] smpboot: CPU 3 is now offline
Mar 14 14:37:52 khashkol kernel: [15745.646907] ACPI: Low-level resume complete
Mar 14 14:37:52 khashkol kernel: [15745.646924] PM: Restoring platform NVS memory
Mar 14 14:37:52 khashkol kernel: [15745.647317] Enabling non-boot CPUs ...
Mar 14 14:37:52 khashkol kernel: [15745.647366] x86: Booting SMP configuration:
Mar 14 14:37:52 khashkol kernel: [15745.647366] smpboot: Booting Node 0 Processor 1 APIC 0x4
Mar 14 14:37:52 khashkol kernel: [15745.649739]  cache: parent cpu1 should not be sleeping
Mar 14 14:37:52 khashkol kernel: [15745.650057] CPU1 is up
Mar 14 14:37:52 khashkol kernel: [15745.650086] smpboot: Booting Node 0 Processor 2 APIC 0x1
Mar 14 14:37:52 khashkol kernel: [15745.652417]  cache: parent cpu2 should not be sleeping
Mar 14 14:37:52 khashkol kernel: [15745.652843] CPU2 is up
Mar 14 14:37:52 khashkol kernel: [15745.652871] smpboot: Booting Node 0 Processor 3 APIC 0x5
Mar 14 14:37:52 khashkol kernel: [15745.655205]  cache: parent cpu3 should not be sleeping
Mar 14 14:37:52 khashkol kernel: [15745.655521] CPU3 is up
Mar 14 14:37:52 khashkol kernel: [15745.657544] ACPI: Waking up from system sleep state S3

After

Mar 17 13:48:32 khashkol kernel: [  284.573893] PM: suspend entry (deep)
Mar 17 13:50:38 khashkol kernel: [    0.000000] Linux version 5.10.0-12-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.103-1 (2022-03-07)
Mar 17 13:50:38 khashkol kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-12-amd64 root=UUID=6e72fa3d-e9d3-4047-ace8-baec24ee7478 ro quiet
Mar 17 13:50:38 khashkol kernel: [    0.000000] x86/fpu: x87 FPU will use FXSAVE
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-provided physical RAM map:
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000094bff] usable
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000000094c00-0x000000000009ffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf77ffff] usable
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf780000-0x00000000bf78dfff] ACPI data
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf78e000-0x00000000bf7cffff] ACPI NVS
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf7d0000-0x00000000bf7dffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf7ed000-0x00000000bfffffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000013bffffff] usable
Mar 17 13:50:38 khashkol kernel: [    0.000000] NX (Execute Disable) protection: active
Mar 17 13:50:38 khashkol kernel: [    0.000000] SMBIOS 2.6 present.
Mar 17 13:50:38 khashkol kernel: [    0.000000] DMI: Acer Aspire M3910/Aspire M3910, BIOS P01-A3         05/17/2010
Mar 17 13:50:38 khashkol kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Mar 17 13:50:38 khashkol kernel: [    0.000000] tsc: Detected 3191.791 MHz processor
Mar 17 13:50:38 khashkol kernel: [    0.003235] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Mar 17 13:50:38 khashkol kernel: [    0.003238] e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 17 13:50:38 khashkol kernel: [    0.003244] last_pfn = 0x13c000 max_arch_pfn = 0x400000000
Mar 17 13:50:38 khashkol kernel: [    0.003248] MTRR default type: uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003249] MTRR fixed ranges enabled:
Mar 17 13:50:38 khashkol kernel: [    0.003251]   00000-9FFFF write-back
Mar 17 13:50:38 khashkol kernel: [    0.003252]   A0000-BFFFF uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003253]   C0000-CFFFF write-protect
Mar 17 13:50:38 khashkol kernel: [    0.003254]   D0000-DFFFF uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003254]   E0000-E7FFF write-through
Mar 17 13:50:38 khashkol kernel: [    0.003255]   E8000-FFFFF write-protect
Mar 17 13:50:38 khashkol kernel: [    0.003256] MTRR variable ranges enabled:
Mar 17 13:50:38 khashkol kernel: [    0.003258]   0 base 13C000000 mask FFC000000 uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003259]   1 base 000000000 mask F00000000 write-back
Mar 17 13:50:38 khashkol kernel: [    0.003260]   2 base 100000000 mask FC0000000 write-back
Mar 17 13:50:38 khashkol kernel: [    0.003261]   3 base 0C0000000 mask FC0000000 uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003262]   4 disabled
Mar 17 13:50:38 khashkol kernel: [    0.003263]   5 disabled
Mar 17 13:50:38 khashkol kernel: [    0.003263]   6 disabled
Mar 17 13:50:38 khashkol kernel: [    0.003264]   7 disabled
Mar 17 13:50:38 khashkol kernel: [    0.004161] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Mar 17 13:50:38 khashkol kernel: [    0.004469] e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
Mar 17 13:50:38 khashkol kernel: [    0.004476] last_pfn = 0xbf780 max_arch_pfn = 0x400000000
Mar 17 13:50:38 khashkol kernel: [    0.013458] found SMP MP-table at [mem 0x000ff780-0x000ff78f]
Mar 17 13:50:38 khashkol kernel: [    0.017237] RAMDISK: [mem 0x349dd000-0x364e5fff]
Mar 17 13:50:38 khashkol kernel: [    0.017241] ACPI: Early table checksum verification disabled
Mar 17 13:50:38 khashkol kernel: [    0.017245] ACPI: RSDP 0x00000000000FA3E0 000014 (v00 ACPIAM)
Mar 17 13:50:38 khashkol kernel: [    0.017250] ACPI: RSDT 0x00000000BF780000 000048 (v01 ACRSYS ACRPRDCT 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017256] ACPI: FACP 0x00000000BF780200 000084 (v01 ACRSYS FACP1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017262] ACPI: DSDT 0x00000000BF7805E0 0068E4 (v01 1AEIP  1AEIP012 00000012 INTL 20051117)
Mar 17 13:50:38 khashkol kernel: [    0.017266] ACPI: FACS 0x00000000BF78E000 000040
Mar 17 13:50:38 khashkol kernel: [    0.017269] ACPI: APIC 0x00000000BF780390 00008C (v01 ACRSYS APIC1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017273] ACPI: MCFG 0x00000000BF780420 00003C (v01 ACRSYS OEMMCFG  20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017277] ACPI: SLIC 0x00000000BF780460 000176 (v01 ACRSYS ACRPRDCT 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017281] ACPI: OEMB 0x00000000BF78E040 000079 (v01 ACRSYS OEMB1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017285] ACPI: HPET 0x00000000BF78A5E0 000038 (v01 ACRSYS OEMHPET  20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017288] ACPI: ASF! 0x00000000BF78A620 000099 (v32 LEGEND I865PASF 00000001 INTL 20051117)
Mar 17 13:50:38 khashkol kernel: [    0.017293] ACPI: AWMI 0x00000000BF78E0C0 00004E (v01 ACRSYS OEMB1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017296] ACPI: SSDT 0x00000000BF78FB60 000363 (v01 DpgPmm CpuPm    00000012 INTL 20051117)
Mar 17 13:50:38 khashkol kernel: [    0.017300] ACPI: Reserving FACP table memory at [mem 0xbf780200-0xbf780283]
Mar 17 13:50:38 khashkol kernel: [    0.017301] ACPI: Reserving DSDT table memory at [mem 0xbf7805e0-0xbf786ec3]
Mar 17 13:50:38 khashkol kernel: [    0.017302] ACPI: Reserving FACS table memory at [mem 0xbf78e000-0xbf78e03f]
Mar 17 13:50:38 khashkol kernel: [    0.017303] ACPI: Reserving APIC table memory at [mem 0xbf780390-0xbf78041b]
Mar 17 13:50:38 khashkol kernel: [    0.017304] ACPI: Reserving MCFG table memory at [mem 0xbf780420-0xbf78045b]
Mar 17 13:50:38 khashkol kernel: [    0.017305] ACPI: Reserving SLIC table memory at [mem 0xbf780460-0xbf7805d5]
Mar 17 13:50:38 khashkol kernel: [    0.017306] ACPI: Reserving OEMB table memory at [mem 0xbf78e040-0xbf78e0b8]
Mar 17 13:50:38 khashkol kernel: [    0.017307] ACPI: Reserving HPET table memory at [mem 0xbf78a5e0-0xbf78a617]
Mar 17 13:50:38 khashkol kernel: [    0.017308] ACPI: Reserving ASF! table memory at [mem 0xbf78a620-0xbf78a6b8]
Mar 17 13:50:38 khashkol kernel: [    0.017309] ACPI: Reserving AWMI table memory at [mem 0xbf78e0c0-0xbf78e10d]
Mar 17 13:50:38 khashkol kernel: [    0.017310] ACPI: Reserving SSDT table memory at [mem 0xbf78fb60-0xbf78fec2]
Mar 17 13:50:38 khashkol kernel: [    0.017319] ACPI: Local APIC address 0xfee00000
Mar 17 13:50:38 khashkol kernel: [    0.017365] No NUMA configuration found
Mar 17 13:50:38 khashkol kernel: [    0.017366] Faking a node at [mem 0x0000000000000000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017379] NODE_DATA(0) allocated [mem 0x13bfd3000-0x13bffcfff]
Mar 17 13:50:38 khashkol kernel: [    0.017870] Zone ranges:
Mar 17 13:50:38 khashkol kernel: [    0.017871]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017873]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017875]   Normal   [mem 0x0000000100000000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017876]   Device   empty
Mar 17 13:50:38 khashkol kernel: [    0.017878] Movable zone start for each node
Mar 17 13:50:38 khashkol kernel: [    0.017880] Early memory node ranges
Mar 17 13:50:38 khashkol kernel: [    0.017881]   node   0: [mem 0x0000000000001000-0x0000000000093fff]
Mar 17 13:50:38 khashkol kernel: [    0.017883]   node   0: [mem 0x0000000000100000-0x00000000bf77ffff]
Mar 17 13:50:38 khashkol kernel: [    0.017884]   node   0: [mem 0x0000000100000000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017886] Initmem setup node 0 [mem 0x0000000000001000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017888] On node 0 totalpages: 1029907
Mar 17 13:50:38 khashkol kernel: [    0.017889]   DMA zone: 64 pages used for memmap
Mar 17 13:50:38 khashkol kernel: [    0.017890]   DMA zone: 21 pages reserved
Mar 17 13:50:38 khashkol kernel: [    0.017891]   DMA zone: 3987 pages, LIFO batch:0
Mar 17 13:50:38 khashkol kernel: [    0.017893]   DMA32 zone: 12190 pages used for memmap
Mar 17 13:50:38 khashkol kernel: [    0.017894]   DMA32 zone: 780160 pages, LIFO batch:63
Mar 17 13:50:38 khashkol kernel: [    0.017895]   Normal zone: 3840 pages used for memmap
Mar 17 13:50:38 khashkol kernel: [    0.017896]   Normal zone: 245760 pages, LIFO batch:63
Mar 17 13:50:38 khashkol kernel: [    0.017900] On node 0, zone DMA: 1 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.017945] On node 0, zone DMA: 108 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.027509] On node 0, zone Normal: 2176 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.027789] On node 0, zone Normal: 16384 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.027910] ACPI: PM-Timer IO Port: 0x808
Mar 17 13:50:38 khashkol kernel: [    0.027913] ACPI: Local APIC address 0xfee00000
Mar 17 13:50:38 khashkol kernel: [    0.027930] IOAPIC[0]: apic_id 6, version 32, address 0xfec00000, GSI 0-23
Mar 17 13:50:38 khashkol kernel: [    0.027932] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Mar 17 13:50:38 khashkol kernel: [    0.027935] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Mar 17 13:50:38 khashkol kernel: [    0.027936] ACPI: IRQ0 used by override.
Mar 17 13:50:38 khashkol kernel: [    0.027937] ACPI: IRQ9 used by override.
Mar 17 13:50:38 khashkol kernel: [    0.027940] Using ACPI (MADT) for SMP configuration information
Mar 17 13:50:38 khashkol kernel: [    0.027942] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Mar 17 13:50:38 khashkol kernel: [    0.027948] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
Mar 17 13:50:38 khashkol kernel: [    0.027966] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Mar 17 13:50:38 khashkol kernel: [    0.027968] PM: hibernation: Registered nosave memory: [mem 0x00094000-0x00094fff]
Mar 17 13:50:38 khashkol kernel: [    0.027968] PM: hibernation: Registered nosave memory: [mem 0x00095000-0x0009ffff]
Mar 17 13:50:38 khashkol kernel: [    0.027969] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000e3fff]
Mar 17 13:50:38 khashkol kernel: [    0.027970] PM: hibernation: Registered nosave memory: [mem 0x000e4000-0x000fffff]
Mar 17 13:50:38 khashkol kernel: [    0.027972] PM: hibernation: Registered nosave memory: [mem 0xbf780000-0xbf78dfff]
Mar 17 13:50:38 khashkol kernel: [    0.027973] PM: hibernation: Registered nosave memory: [mem 0xbf78e000-0xbf7cffff]
Mar 17 13:50:38 khashkol kernel: [    0.027974] PM: hibernation: Registered nosave memory: [mem 0xbf7d0000-0xbf7dffff]
Mar 17 13:50:38 khashkol kernel: [    0.027974] PM: hibernation: Registered nosave memory: [mem 0xbf7e0000-0xbf7ecfff]
Mar 17 13:50:38 khashkol kernel: [    0.027975] PM: hibernation: Registered nosave memory: [mem 0xbf7ed000-0xbfffffff]
Mar 17 13:50:38 khashkol kernel: [    0.027976] PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xfedfffff]
Mar 17 13:50:38 khashkol kernel: [    0.027977] PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Mar 17 13:50:38 khashkol kernel: [    0.027978] PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xffafffff]
Mar 17 13:50:38 khashkol kernel: [    0.027978] PM: hibernation: Registered nosave memory: [mem 0xffb00000-0xffffffff]
Mar 17 13:50:38 khashkol kernel: [    0.027981] [mem 0xc0000000-0xfedfffff] available for PCI devices
Mar 17 13:50:38 khashkol kernel: [    0.027982] Booting paravirtualized kernel on bare hardware
Mar 17 13:50:38 khashkol kernel: [    0.027985] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Mar 17 13:50:38 khashkol kernel: [    0.032311] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
Mar 17 13:50:38 khashkol kernel: [    0.032697] percpu: Embedded 58 pages/cpu s200536 r8192 d28840 u262144
Mar 17 13:50:38 khashkol kernel: [    0.032706] pcpu-alloc: s200536 r8192 d28840 u262144 alloc=1*2097152
Mar 17 13:50:38 khashkol kernel: [    0.032708] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Mar 17 13:50:38 khashkol kernel: [    0.032748] Built 1 zonelists, mobility grouping on.  Total pages: 1013792
Mar 17 13:50:38 khashkol kernel: [    0.032749] Policy zone: Normal
Mar 17 13:50:38 khashkol kernel: [    0.032751] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-12-amd64 root=UUID=6e72fa3d-e9d3-4047-ace8-baec24ee7478 ro quiet

migf · Installation

Thank you for all your recent posts!

alexkemp wrote:
sudo apt install libpam-elogind 

In fact this package was already installed, so I installed

libpolkit-gobject-elogind-1-0

and the two console-kit related packages were removed as fsmithred mentioned.

fsmithred wrote:
If you're still having trouble with suspend after you get the packages all straightened out, you might take a look at this page: https://wiki.ubuntu.com/DebuggingKernelSuspend

I read it and some stuiff linked from it but I couldn't do anything: they say one should trace what happens at the kernel level assuming the file

/sys/power/pm-trace

exists what is not the case here.

I also found some pages that mentioned changes that could be made on

/proc/acpi/awake

that here has

Device  S-state   Status   Sysfs node
P0P1      S4    *disabled  pci:0000:00:01.0
P0P3      S4    *disabled
P0P4      S4    *disabled
P0P5      S4    *disabled
P0P6      S4    *disabled
BR1E      S4    *disabled  pci:0000:00:1e.0
PS2K      S4    *enabled   pnp:00:02
                *disabled  serio:serio0
PS2M      S4    *disabled  pnp:00:03
BR20      S4    *disabled  pci:0000:00:1c.0
BR21      S4    *disabled
BR22      S4    *disabled  pci:0000:00:1c.2
BR23      S4    *disabled
BR24      S4    *disabled
BR25      S4    *disabled
BR26      S4    *disabled
BR27      S4    *disabled
EUSB      S3    *enabled   pci:0000:00:1d.0
USB0      S3    *disabled
USB1      S3    *disabled
USB2      S3    *disabled
USB3      S3    *disabled
USBE      S3    *enabled   pci:0000:00:1a.0
USB4      S3    *disabled
USB5      S3    *disabled
USB6      S3    *disabled
GBE       S4    *disabled
SLPB      S4    *disabled

It may happen that EUSB stands for the keyboard but I don't know how to check that.

Should I start a new thread on this and mark the current thread as solved?

migf · Installation

alexkemp wrote:
Something else for you to look at.

Thanks! I compared with my list here and there is a difference here: I have consolekit and libpolkit-gobject-consolekit-1-0 instead of libpolkit-gobject-elogind-1-0. Do you think I should change to your configuration by installing libpolkit-gobject-elogind-1-0?

migf · Installation

Well, the suspend and other options can now be used but when I tried to suspend the system it went into a suspended state with the disks still spinning and the only way to get back from this was a hard reset. This was what happened yesterday when I run pm-suspend.

I tried to find in the syslog something about this but to no avail. Can this be a problem with the new linux kernel (5.10.0-12)?

migf · Installation

Yes, you are right: I have elogind, libpam-elogind and libelogind0 installed with no losses (as far as I can see).

I am going to reboot and see if there is some visible change.

migf · Installation

Thanks for your answers but I am a bit at a loss on what to do: installing all at once with apt-get does not solve the problem, and with aptitude it lists a still larger list of removals that include libsystemd0 (and so creating all those dependency problems as abovd). I think that the problem here is that a lot of packages depend exclusively on libsystemd0 and do not recognize libelogind0 as a replacement to it.

Is there any safe way of letting normal users in a certain group to run shutdown and any other command related to suspending and so on? This would probably solve the issue I have.

migf · Installation

The list is not really of removals but of dependencies, and installing libelogind0 gives a similar one if not exactly the same:

dpkg: libsystemd0:amd64: dependency problems, but removing anyway as you requested:
 xserver-xorg-core depends on libsystemd0.
 xscreensaver depends on libsystemd0 (>= 243).
 vlc-plugin-base:amd64 depends on libsystemd0.
 smartmontools depends on libsystemd0.
 sane-utils depends on libsystemd0.
 rpcbind depends on libsystemd0.
 pulseaudio depends on libsystemd0.
 ppp depends on libsystemd0.
 openssh-server depends on libsystemd0.
 libwebkit2gtk-4.0-37:amd64 depends on libsystemd0.
 libwbclient0:amd64 depends on libsystemd0.
 libvte-2.91-0:amd64 depends on libsystemd0 (>= 220).
 libspa-0.2-modules:amd64 depends on libsystemd0.
 libpulse0:amd64 depends on libsystemd0.
 libpipewire-0.3-modules:amd64 depends on libsystemd0.
 libjavascriptcoregtk-4.0-18:amd64 depends on libsystemd0.
 libgnome-desktop-3-19:amd64 depends on libsystemd0.
 libbrlapi0.8:amd64 depends on libsystemd0.
 libapt-pkg5.0:amd64 depends on libsystemd0 (>= 221).
 jackd2 depends on libsystemd0.
 gvfs-daemons depends on libsystemd0.
 fluidsynth depends on libsystemd0.
 emacs-gtk depends on libsystemd0.
 cups-daemon depends on libsystemd0.

So I went back, removing libelogind0 and installing libsystemd0.

migf · Installation

Yes, I have rebooted many times, in particular in a hard way after an unrecoverable suspend with pm-suspend, and after slim becoming unresponsive, probably due to some problem with firefox.

Trying your suggestion:

The following packages will be REMOVED:
  libpam-ck-connector libsystemd0
The following NEW packages will be installed:
  elogind libelogind0 libpam-elogind policykit-1 policykit-1-gnome

Removing
dpkg: libsystemd0:amd64: dependency problems, but removing anyway as you requested:
 xserver-xorg-core depends on libsystemd0.
 xscreensaver depends on libsystemd0 (>= 243).
 vlc-plugin-base:amd64 depends on libsystemd0.
 smartmontools depends on libsystemd0.
 sane-utils depends on libsystemd0.
 rpcbind depends on libsystemd0.
 pulseaudio depends on libsystemd0.
 ppp depends on libsystemd0.
 openssh-server depends on libsystemd0.
 libwebkit2gtk-4.0-37:amd64 depends on libsystemd0.
 libwbclient0:amd64 depends on libsystemd0.
 libvte-2.91-0:amd64 depends on libsystemd0 (>= 220).
 libspa-0.2-modules:amd64 depends on libsystemd0.
 libpulse0:amd64 depends on libsystemd0.
 libpipewire-0.3-modules:amd64 depends on libsystemd0.
 libjavascriptcoregtk-4.0-18:amd64 depends on libsystemd0.
 libgnome-desktop-3-19:amd64 depends on libsystemd0.
 libbrlapi0.8:amd64 depends on libsystemd0.
 libapt-pkg5.0:amd64 depends on libsystemd0 (>= 221).
 jackd2 depends on libsystemd0.
 gvfs-daemons depends on libsystemd0.
 fluidsynth depends on libsystemd0.
 emacs-gtk depends on libsystemd0.
 cups-daemon depends on libsystemd0.

well, a lot of installed things will not work...

So, I think the right thing to do is to abort now and ask for your help again...

migf · Installation

Here is the output of the command:

ii  consolekit                             1.2.1-8                            amd64        framework for defining and tracking users, sessions and seats
ii  gir1.2-polkit-1.0                      0.105-31+devuan2                   amd64        GObject introspection data for PolicyKit
ii  libpam-cap:amd64                       1:2.44-1                           amd64        POSIX 1003.1e capabilities (PAM module)
ii  libpam-ck-connector:amd64              1.2.1-8                            amd64        ConsoleKit PAM module
ii  libpam-gnome-keyring:amd64             3.36.0-1                           amd64        PAM module to unlock the GNOME keyring upon login
ii  libpam-modules:amd64                   1.4.0-9+deb11u1                    amd64        Pluggable Authentication Modules for PAM
ii  libpam-modules-bin                     1.4.0-9+deb11u1                    amd64        Pluggable Authentication Modules for PAM - helper binaries
ii  libpam-runtime                         1.4.0-9+deb11u1                    all          Runtime support for the PAM library
ii  libpam0g:amd64                         1.4.0-9+deb11u1                    amd64        Pluggable Authentication Modules library
ii  libpolkit-agent-1-0:amd64              0.105-31+devuan2                   amd64        PolicyKit Authentication Agent API
ii  libpolkit-gobject-1-0                  0.105-31+devuan2                   all          PolicyKit Authorization API
ii  libpolkit-gobject-consolekit-1-0:amd64 0.105-25+devuan9                   amd64        PolicyKit Authorization API
ii  libpolkit-qt5-1-1:amd64                0.112.0-5                          amd64        PolicyKit-qt5-1 library
ii  libupower-glib1:amd64                  1:0.9.23-2+devuan1.3               amd64        abstraction for power management - shared library
ii  libupower-glib3:amd64                  0.99.11-2                          amd64        abstraction for power management - shared library
rc  policykit-1                            0.105-25+devuan9                   amd64        framework for managing administrative policies and privileges
rc  policykit-1-gnome                      0.105-7                            amd64        authentication agent for PolicyKit
ii  upower                                 1:0.9.23-2+devuan1.3               amd64        abstraction for power management

I strictly followed the instructions in the Devuan site https://www.devuan.org/os/documentation … o-chimaera:

 apt-get update
 apt-get upgrade
 apt-get dist-upgrade

after changing sources.list to

deb http://deb.devuan.org/merged chimaera main
deb http://deb.devuan.org/merged chimaera-updates main
deb http://deb.devuan.org/merged chimaera-security main
#deb http://deb.devuan.org/merged chimaera-backports main

migf · Installation

You are welcome!

Any idea on how to make available the greyed logout options?

migf · Installation

Maybe I have wrongly taken

accessible

as meaning unavailable, instead of supporting I/O means for impaired people, If that is the case my apologies.

The officially official Devuan Forum!

#1 Re: Hardware & System Configuration » [SOLVED] Installing firmware not yet in Devuan nor Debian packages » 2022-11-04 19:12:24

#2 Re: Hardware & System Configuration » [SOLVED] Installing firmware not yet in Devuan nor Debian packages » 2022-11-04 18:09:11

#3 Re: Hardware & System Configuration » [SOLVED] Installing firmware not yet in Devuan nor Debian packages » 2022-11-04 12:31:56

#4 Re: Hardware & System Configuration » [SOLVED] Installing firmware not yet in Devuan nor Debian packages » 2022-11-03 18:36:41

#5 Re: Hardware & System Configuration » [SOLVED] Installing firmware not yet in Devuan nor Debian packages » 2022-11-01 19:40:25

#6 Hardware & System Configuration » [SOLVED] Installing firmware not yet in Devuan nor Debian packages » 2022-11-01 18:07:27

#7 Re: Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-21 16:00:56

#8 Re: Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-21 14:58:36

#9 Re: Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-21 12:15:33

#10 Re: Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-21 10:19:55

#11 Hardware & System Configuration » [SOLVED] Realtet 8852 wireless in Chimaera » 2022-10-20 17:29:00

#12 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-23 17:41:31

#13 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-23 10:34:44

#14 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-22 21:20:36

#15 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-21 14:02:27

#16 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-18 18:04:21

#17 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-17 21:18:42

#18 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-17 14:19:33

#19 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-17 13:42:03

#20 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-17 10:19:48

#21 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-16 19:38:39

#22 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-16 18:56:04

#23 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-16 17:08:29

#24 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-16 13:30:10

#25 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-16 13:00:07

Board footer