You are not logged in.
Have you made sure the kernel modules are available (like sch_cbq, sch_sfq and sch_ingress)? Or maybe it's a udev issue, and the modules need to be loaded manually?
ok
peculiar; the script worked fine for me on daedalus; it's the same package version and script.
Which kernel version? And what do you get from:
# tc qdisc show
Did you install it? It does depend on iproute2 (or iproute)
And then if this is ceres rather than daedalus anything (else) is possible
Sounds good.
And maybe as a first thing, one or two people should involve themselves with the various Devuan discussion channels to set up and maintain a "The Todo List" area on the wiki.
@semil, whan I just now installed gpm and tried it on a console, it happily responded to tapping as clicking. It's missing out on other fancy stuff that I've set up on synclient for X11 but it handls single, double tripple taps well.
Have you verified that /etc/gpm.conf says device=/dev/input/mice (and type=exps2) ?
Yes, that's what it says, isn't it?
The current installation does not have a merged-/usr layout.
This is unsupported and unpacking libc6 would break the system.
Refusing to unpack. Please install the usrmerge package and try again.
Note that each desktop environment, whether it is kde or xfce or lxqt, is a largish stack of packages that have been made to work together, and in some cases the different desktop environments have competing demands of packages. Basically as a concept, having multiple DE's installed is not like having a house with many rooms, but more like having a single-room house with several collections of furniture in it.
E.g. one fundamental competition with your DE collection is wether the display server is Xorg or Wayland (some require the one or the other, some kind of work with either) and there are numerous of conflicting demands stemming from that. And I believe slim if you've installed that requires Xorg whereas sddm might handle either Xorg or Wayland although might need configuration choice about which to use.
Afaik startx is a completely different program which is supposed to run an Xorg as display server, and then have the desired auto-started programs nominated in an .xinitrc (or something similar).
I think you would have an easier task if you go back and rather make a single choice than pile up multiple options without bothering about or knowing how they compete.
Yes quite possibly.
Check /prroc/acpi/wakeup for enabled wakeup sources.
The mapping from acpi names to devices may be difficult; this worked for me:
( grep enable /proc/acpi/wakeup | sed 's|.*0000:|-|' ; lspci ) | \
sort | grep -A1 '^-' | grep -v '^-'
It's possible to disable them; I'd need to google it.
Well, you'd want the forked packages.
I still think your issue is that the USB host (xhci_hcd) driver fails to suspend, which the log says, and it willl need explicit unloading beforehand. I.e. it's not related to which Xorg packages you have.
Maybe worth a try to install pm-utils and trial it with the pm-suspend command?
Tom, did your painstaking creation of /etc/network/interfaces configurations include a line like
auto ethX0 ethX1
which is what ifupdown requires in order to auto-configure those interfaces when started?
There is e.g. man 5 interfaces for some llight reading about this.
Usually one would install task-xfce-desktop and be happy with that. It would bring in that s.c. "standard" xfce desktop environment with all its bells and whistles. Though it appears you want something else.
If you want to do it with tasksel I think you need to reconfigure rather than install.
EDIT: no I was wrong about tasksel; you just run it as root.
hmm that's from pm-utils ... I guess I assumed you suspended via pm-suspend but apparently you suspend in some other way, so you may need to use its way of unloading modules.
try with
SUSPEND_MODULES=xhci_hcd
in /etc/pm/config.d/something
EDIT: That of course will stop wake-up via USB keyboard...
???
2024-06-02T22:01:39.784035+02:00 rh060 kernel: [ 1020.772430] xhci_hcd 0000:05:00.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x20 [usbcore] returns -16
2024-06-02T22:01:39.784036+02:00 rh060 kernel: [ 1020.772454] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
2024-06-02T22:01:39.784036+02:00 rh060 kernel: [ 1020.772464] xhci_hcd 0000:05:00.0: PM: failed to suspend async: error -16
2024-06-02T22:01:39.784037+02:00 rh060 kernel: [ 1021.246710] PM: Some devices failed to suspend, or early wake event detected
This looks like "the broken xhci_hcd problem" from 2015 is back... at the time it was solved by unloading the module before sleep and loading it back on resume.
You should then click "Mark SOLVED" to let the forum s/w automagically edit the initial title... or edit it by hand if you prefer.
It appears that the documentation page you linked
https://www.devuan.org/os/documentation … all-devuan
skips a couple of dialoges:
1. between its 9 and 10 is a dialogue to select which disk to work with, and
2. between its 10 and 11 is a dialog that presents an overview of all disk layouts.
If the #11 dialog in your case includes sdb, you need to choose the "No" option to go back to the partitioner and undo any partitioning of sdb that you have chosen.
Fair enough. afaik it's the very same software, but obviously there's something different.
I would say that technically the story is that the partitioning software shows all avaiable drives of the system, and it's the person installing that decides and selects which drives to partition and how to use them for installation.
However, it's the software is the debian package partman. If you feel strongly about it you should lodge a bug report about the package to bugs.debian.org.
If you install imagemagick-6.q16 you get convert and display, and then you can amuse yourself with commands like:
$ convert \
https://kathleenkarlsen.com/wp-content/uploads/2021/12/Medicine-Buddha-Mantra-Illustration.png \
-fill black -pointsize 28 -annotate +10+30 "Om Mani Padme Hum" \
PNG:- | display -
You may try with a TAB and then add console=ttyS0,115200 to the boot parameters somewhere early, and then you also need to tell qemu to offer the serial on the console perhaps multiplexed with the qemu monitor by adding -serial mon:stdio to its arguments. That will do well until the first reboot where you also need to have configured the bootup init system to offer serial login.
@tyrlak, make sure your xserver-xorg-core and xserver-common packages are version 2:21.1.7-3+deb12u5devuan1 from devuan-security.
Which issue?
Clearly mount doesn't find any partition with label DEVUAN501 so the preamble moves on to the Ventoy patch in order to loopback the ISO image if it finds that, which it does. The loopback device is next presented to the installer which then is quite happy using that.
First cabs off the rank would be:
1. Is this a PATH problem? (Non-root user typically lacks /sbin and /usr/sbin in PATH)
2. Or a problem due to that /bin/sh is dash rather than bash ?
Sounds good. (though I wouldn't keep my software at a microsoft site)
Perhaps check out https://www.debian.org/doc/manuals/maint-guide/ and get your package into the debian collection...