You are not logged in.
Thanks.
Hi, Altoid.
2 facts:
- just because it works for you doesn't mean that the problem doesn't exist for others
- your answer is out of use to me, and especially does not answer my question. Devuan Stable is not egual to Unstable. Not same libs, etc.
Hi, all.
As I wroted on https://dev1galaxy.org/viewtopic.php?pid=36593#p36593, a bug is open because Virtualbox not function correctly on kernel ≥ 5.10 (including 5.18)
Wait'n see a new version!
PS: One tips, reboot on oldier kernel…
(if available)
Today,
I cant start my VM Virtualbox on my Ceres. Crash!
$ uname -a
Linux pc-z 5.18.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.2-1 (2022-06-06) x86_64 GNU/Linux
$ vboxmanage --version
6.1.34_Debianr150636
This issue #20914 seems to match.
Here a post on virtualbox forum.
Is it possible to switch to an older kernel? If yes, how?
(knowing that apparently 5.10 seems to be affected too)
@fsmithred: ty!
@fsmithred: the connection about usrmerge?
On french forum debian-fr.org, one user specifies que dm-verity use `mount` binary:
# dm-verity support
if [ "${DISABLE_DM_VERITY:-}" != "true" ] && [ "${DISABLE_DM_VERITY:-}" != "yes" ]
then
[ "${QUIET}" ] || echo -n " dm-verity"
manual_add_modules dm-verity
# The BusyBox mount does not support dm-verity so we use the util-linux version.
copy_exec /usr/bin/mount /bin
fi
On Devuan, the mount binary is not, by default, on /usr/bin/mount, just on /bin/mount. Either, I create a symlink or install usrmerge. I did not want to create a symbolic link, I installed usrmerge.
Before usrmerge:
$ which -a mount
/bin/mount
After:
$ which -a mount
/usr/bin/mount
/bin/mount
@rolfie: Daedalus is not an Unstable version. It's the future "stable", actual "testing".
See: https://www.devuan.org/os/releases
Installing the `usrmerge` package solves the problem; update continues without fails.
---
@Head_on_a_stick: purge done! (but only live-boot-initramfs-tools was installed)
Hi, @Head_on_a_stick
From where did you obtain that hook? It shouldn't be present in an installed system.
I dont known!
Hi,
Today, during my weekly update, the process of apt fails with this error:
# apt update && apt upgrade -y
(...)
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Paramétrage de initramfs-tools (0.141) ...
update-initramfs: deferring update (trigger activated)
Traitement des actions différées (« triggers ») pour initramfs-tools (0.141) ...
update-initramfs: Generating /boot/initrd.img-5.17.0-1-amd64
live-boot: core filesystems dm-verityE: /usr/share/initramfs-tools/hooks/live failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.17.0-1-amd64 with 1.
dpkg: erreur de traitement du paquet initramfs-tools (--configure) :
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Des erreurs ont été rencontrées pendant l'exécution :
initramfs-tools
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Next, I tried a `dpkg configure` as:
# dpkg --configure -a
Paramétrage de initramfs-tools (0.141) ...
update-initramfs: deferring update (trigger activated)
Traitement des actions différées (« triggers ») pour initramfs-tools (0.141) ...
update-initramfs: Generating /boot/initrd.img-5.17.0-1-amd64
live-boot: core filesystems dm-verityE: /usr/share/initramfs-tools/hooks/live failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.17.0-1-amd64 with 1.
dpkg: erreur de traitement du paquet initramfs-tools (--configure) :
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Des erreurs ont été rencontrées pendant l'exécution :
initramfs-tools
Same result!
For the `update-initramfs -uv` command, see the paste : https://0x0.st/omms.txt
How can I fix this?
I solved this problem to reinstall xserver-xorg, xserver-xorg-input-all packages!
Now, this run correctly.
but, slim start, it's not the problem. the problem is that keyboard, mouse not respond!
(same result if I use startx startxfce4 to connect directly on xcfe session... keyboard and mouse are not functionals)
Hi.
for the rc-status, see https://0x0.st/oPZX.txt
I added dbus and elogind services:
# rc-update add dbus
* service dbus added to runlevel sysinit
# rc-update add elogind
* service elogind added to runlevel sysinit
after, reboot...
but same problem, no keyboard on slim!
elogind is installed but cant run!
# service elogind status
elogind is not running... failed
# service elogind start
Starting session management daemon: elogind
elogind-daemon[2075]: Failed to connect to system bus: No such file or directory
elogind-daemon[2075]: Failed to fully start up daemon: No such file or directory
startx is not relevant, now? if not, how start X session ?
Hi,
I use Devuan Ceres. yesterday I upgraded my station by using the "full-upgrade" option to apt.
The process ran correctly, informed me than a new kernel (5.16) installed, and all needed services restarted.
Some packages are marked to uninstall...
My DE is XFCE, The service manager is OpenRC.
I rebooted on the new kernel. But, the X session cant start. Slim is show, but no keyboard input is working, as if it were physically disconnected.
I dont know how resolve this problem.
1/ the recovery mode run!
2/ keyboard and mouse run correctly on the terminal, but when the X start, those are not functionals.
I attempted to "reinstall" xserver-common, and "xserver-xorg-legacy" packages, but this not resolve.
If I start the X session by call "startd", Xfce session display but keyboard and mouse seems to deactivate. no response.
to make sure it's not a problem with the new kernel, I reboot under the old kernel (5.15.x): same problem; unable to connect because keyboard not responds.
I suspect a problem with dbus, because when I reinstalled "xserver-common" package, I've this message:
Reloading system message bus config... Failed to open connection to "system" message bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
invoke-rc.d: initscript dbus, action "force-reload" failed.
Failed to open connection to "system" message bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
How restore X session functional?
OK, see on IRC #iwd: need to remove file /etc/iwd/main.conf
solved!
Hi,
Today, I want use my dongle USB, but when I start iwd, it refuses:
$ iwctl station list
The name net.connman.iwd was not provided by any .service files
Failed to retrieve IWD dbus objects, quitting...
But connman seems running:
$ sudo service connman status
connmand is running.
any suggestion?
---
$ cat /etc/iwd/main.conf
[General]
EnableNetworkConfiguration=true
[Network]
RoutePriorityOffset=200
NameResolvingService=resolvconf
OK, With iwd and connman, It's run! Yeahhh.
All run correctly, on IPv4 and IPv6!
Thanks @all, but specially @HoaS
No, it's not all things!
But others lines concern iface lo and eth0. Do you want really?!
The file start with this line:
source /etc/network/interfaces.d/*
(…)
allow-hotplug wlx00e0250d7ef2
iface wlx00e0250d7ef2 inet dhcp
# wpa-driver wext
# wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
wpa-ssid SH
wpa-psk ***xyz***
wpa_supplicant.conf:
$ cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/run/wpa_supplicant
update_config=1
network={
id_str="sh"
ssid="SH"
psk=***xyz***
}
/etc/network/interfaces:
allow-hotplug wlx00e0250d7ef2
iface wlx00e0250d7ef2 inet dhcp
# wpa-driver wext
# wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
wpa-ssid SH
wpa-psk ***xyz***
Hi all.
OK, before yours replies, I set the wpa_supplicant file config.
(today, I installed too connman; wicd seems not available - it's not the problem).
When I plug the dongle USB, it receives one adress IP, but not the gateway's one.
(but, my Android smartphone receive correctly the datas, and can connect on the Internet, for instance)
It seems when I connect with the dongle USB, it not receives or configure the default route:
$ ip route
192.168.xyz.0/24 dev wlx00e0250d7ef2 proto kernel scope link src 192.168.xyz.144
When I use the ethernet wired:
$ ip route
default via 192.168.abc.1 dev eth0
192.168.abc.0/24 dev eth0 proto kernel scope link src 192.168.abc.47
192.168.abc.1 dev eth0 scope link
192.168.xyz.0/24 dev wlx00e0250d7ef2 proto kernel scope link src 192.168.xyz.144
One idea?
$ apt policy eudev
eudev:
Installé : 3.2.9-8
Candidat : 3.2.9-8
Table de version :
*** 3.2.9-8 500
500 http://deb.devuan.org/merged ceres/main amd64 Packages
100 /var/lib/dpkg/status
Why is it so so complicated?
Hi, all
I bought few days ago a usb dongle, recognized by lsusb as:
Bus 001 Device 003: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
On dmesg:
[ 878.416457] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
[ 878.531504] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[ 878.551495] mt7601u 1-1.4:1.0: firmware: direct-loading firmware mt7601u.bin
[ 878.551504] mt7601u 1-1.4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146____
[ 878.956971] mt7601u 1-1.4:1.0: EEPROM ver:0d fae:00
[ 879.183994] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 879.184474] usbcore: registered new interface driver mt7601u
(…)
[ 879.258512] mt7601u 1-1.4:1.0 wlx00e0250d7ef2: renamed from wlan0
lsmod:
$ lsmod | grep mt
mt7601u 135168 0
mac80211 983040 1 mt7601u
cfg80211 974848 2 mt7601u,mac80211
usbcore 323584 6 xhci_hcd,ehci_pci,usbhid,mt7601u,ehci_hcd,xhci_pci
module seems loaded!
ip address:
3: wlx00e0250d7ef2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:25:0d:7e:f2 brd ff:ff:ff:ff:ff:ff
iw show the hardware:
$ sudo iw dev wlx00e0250d7ef2 info
Interface wlx00e0250d7ef2
ifindex 3
wdev 0x1
addr 00:e0:25:0d:7e:f2
type managed
wiphy 0
txpower 0.00 dBm
rfkill show no block:
$ sudo rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
I installed wpa_supplicant, wpa_gui… but it's not appear!
$ sudo wpa_cli -i wlx00e0250d7ef2
wpa_cli v2.9
Copyright (c) 2004-2019, Jouni Malinen <j@w1.fi> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Interactive mode
Could not connect to wpa_supplicant: wlx00e0250d7ef2 - re-trying
^C
How can I use this USB hardware?
Xfce was not updated correctly fully.
Now, its good!
ty all
OK, I tried to with https://git.devuan.org/devuan/installer-iso.
I modified Makefile and pool/Makefile as:
Makefile:
(…)
DISTNAME = ceres
DISTVERSION = 2020.12.12
(…)
pool/Makefile:
(…)
CODENAME := ceres
(…)
But that failed:
$ make ISO=netinstall
Makefile:33: ISOTREE=build/amd64/netinstall
dependencies.mk:16: dependencies.mk: ARCH=amd64
boot-bios-isolinux.mk:12: build/amd64/netinstall/boot/isolinux/
boot-efi-grub.mk:15: build/amd64/netinstall/boot/grub/
win32-loader.mk:8: build/amd64/netinstall/
udeb-sets.mk:1: UDEBSELECT = kernel base
udeb-sets.mk:3: "UDEBS:kernel for KERNELVERSION=5.9.0-4-amd64-di"
udeb-sets.mk:59: "UDEBS:base"
kernel.mk:6: INITRD_BUILDDIR = build/amd64/initrd
packages.mk:6: ISO = netinstall (of NETINSTALL INSTALL DVD1 CD2 CD3 CD4)
firmware.mk:4: adding links for all *firmware* and *microcode* in the pool
makeiso.mk:13: Devuan 2020.12.12 = Devuan ceres 2020.12.12
saverun.mk:6: SAVERUNDIR = content/ceres-2020.12.12-amd64/netinstall-20201212204339
make -C pool ISO=NETINSTALL
make[1] : on entre dans le répertoire « /home/me/Documents/Projets/installer-iso/pool »
Makefile:20: kernel for amd64 is linux-image-amd64
make[1]: *** Aucune règle pour fabriquer la cible « /var/lib/apt/lists/pkgmaster.devuan.org_merged_dists_ceres_main_binary-amd64_Packages », nécessaire pour « library-amd64-main ». Arrêt.
make[1] : on quitte le répertoire « /home/me/Documents/Projets/installer-iso/pool »
make: *** [packages.mk:15 : pool.NETINSTALL] Erreur 2
The loose!
And basta, I abandonne too… because I dont see/known what need changes.
---
I can at least generate the mini.iso image of the modified debian-installer for devuan ceres, apparently!
(but, for the moment, I cant install qemu, I cant check if runs correctly)