You are not logged in.
I worked on such an X installation back in 1987,88. Simple graphics, small network traffic. , low res pixel-centric graphics with no rendering necessary.
Drawing electrical schematics.
What do i miss ?
about one week of work , including the learning curve.
I did that once under S.u.S.E. (<=7.3, < Y2003) . It included compiling a stripped partly non modular kernel for the clients, which had the network card driver compiled in. Once that works, it can pull other modules from the server. All what was not needed, was not compiled to obtain the smallest kernel.
And the distributed X11 server / xclient architecture is interesting .
Nice if you have many many many clients , no distributed maintenance.
I dont know, how this is today with wayland. see here :
https://en.wikipedia.org/wiki/Wayland_( … land_and_X
Lots of rendering today, lots of network traffic today, if distributed and wrong distribution of graphic load..
Power up the client :
PXE
DHCP,
TFTP,
NFS,
(DNS) and only then LTSP ,
and then X11 client server.
And then login on the Thin client
cat /etc/default/grub
....
# check for other OS https://www.omgubuntu.co.uk/2021/12/grub-doesnt-detect-windows-linux-distros-fix
GRUB_DISABLE_OS_PROBER=false
.....
must set to false
Have upgraded to daedalus
Problem has been solved efficiently on the NVIDIA Board See there:
https://forums.developer.nvidia.com/t/k … ore/287257
Just continuing to shout "everyone needs to get on a bike"
Didi anyone say that?
Just for me: I did 30000km in 6 years with my car, 5000 km / year (3000miles) and most of the time it is standing around for a week or so. A waste of resources.
I have 6 options : own car, train, bus, bicycle and walking and an electric rental car here in the village.
No car is MY economic solution.
I choose to live here because of the train station and not in the next village w/o train station.
Why should I keep a car (fuel or electric)?
Those with a huge toolbox and a selection of spare parts are a different task. They might have an electric workshop truck - on wheels .
Electric cars come with high capital cost and it is mandatory , that they roll all the time. Probably rental is the solution .
The old school "living far from dense population" becomes more and more uneconomic, when cheap fuel disappears.
And transport without modal change is also a thing of the past, when transport chains can be organized by internet.
Currently my setup works with xorg.conf
Section "ServerLayout"
Identifier "Schreibtisch"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
# FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "built-ins"
EndSection
Section "Module"
Load "glx"
Load "intel"
Load "nvidia"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "libinput"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "libinput"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Lenovo"
ModelName "L24e-30"
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Lenovo"
ModelName "L1951p"
Option "DPMS"
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
Section "Device"
VendorName "NVIDIA Corporation"
Identifier "Card1"
Driver "nvidia"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
SubSection "Display"
Viewport 0 3
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 3
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 3
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 3
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 3
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 3
Depth 24
Modes "1440x900"
EndSubSection
EndSection
Section "ServerFlags"
Option "Xinerama" "1"
Option "AutoAddDevices" "true"
Option "AutoAddGPU" "false"
Option "AutoEnableDevices" "true"
EndSection
Section "Extensions"
Option "COMPOSITE" "Disable"
EndSection
but Xrandr does not detect the 2nd monitor
from terminal:
xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 530mm x 300mm
1920x1080 60.00*+ 74.97 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.90
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 72.81 60.00 59.94
720x400 70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
With Xinerama 0 the right screen (nvidia) remains dark.
With Xinerama 1, the virtual screen extend over both monitors. Mouse moves and windows can be shifted around.
the Xorg.0.log is this
[ 62246.167]
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[ 62246.167] Build Operating System: linux Debian
[ 62246.167] Current Operating System: Linux thinkstation 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64
[ 62246.167] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-28-amd64 root=UUID=e26f69aa-878b-46ca-8a16-c90ac9e06e62 ro quiet 2
[ 62246.167] Build Date: 22 January 2024 06:21:42AM
[ 62246.167] xorg-server 2:1.20.11-1+deb11u11 (https://www.debian.org/support)
[ 62246.167] Current version of pixman: 0.40.0
[ 62246.167] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 62246.167] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 62246.167] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 10:17:31 2024
[ 62246.167] (==) Using config file: "/etc/X11/xorg.conf"
[ 62246.167] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 62246.167] (==) ServerLayout "Schreibtisch"
[ 62246.167] (**) |-->Screen "Screen0" (0)
[ 62246.167] (**) | |-->Monitor "Monitor0"
[ 62246.167] (**) | |-->Device "Card0"
[ 62246.167] (**) |-->Screen "Screen1" (1)
[ 62246.167] (**) | |-->Monitor "Monitor1"
[ 62246.167] (**) | |-->Device "Card1"
[ 62246.167] (**) |-->Input Device "Mouse0"
[ 62246.167] (**) |-->Input Device "Keyboard0"
[ 62246.167] (**) Option "Xinerama" "0"
[ 62246.167] (**) Option "AutoAddDevices" "true"
[ 62246.167] (**) Option "AutoEnableDevices" "true"
[ 62246.167] (**) Option "AutoAddGPU" "false"
[ 62246.167] (**) Automatically adding devices
[ 62246.167] (**) Automatically enabling devices
[ 62246.167] (**) Not automatically adding GPU devices
[ 62246.167] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 62246.167] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 62246.167] Entry deleted from font path.
[ 62246.167] (**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins,
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 62246.167] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 62246.167] (**) Extension "COMPOSITE" is enabled
[ 62246.167] (II) Loader magic: 0x564bf6f48e40
[ 62246.167] (II) Module ABI versions:
[ 62246.167] X.Org ANSI C Emulation: 0.4
[ 62246.167] X.Org Video Driver: 24.1
[ 62246.167] X.Org XInput driver : 24.1
[ 62246.167] X.Org Server Extension : 10.0
[ 62246.168] (++) using VT number 7
[ 62246.168] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 62246.168] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 62246.168] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 62246.183] (--) PCI: (0@0:2:0) 8086:3e92:17aa:3138 rev 0, Mem @ 0x62000000/16777216, 0x40000000/268435456, I/O @ 0x00004000/64
[ 62246.183] (--) PCI:*(1@0:0:0) 10de:1c30:10de:11b3 rev 161, Mem @ 0x63000000/16777216, 0x50000000/268435456, 0x60000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/131072
[ 62246.183] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 62246.183] (II) LoadModule: "glx"
[ 62246.183] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 62246.183] (II) Module glx: vendor="X.Org Foundation"
[ 62246.183] compiled for 1.20.11, module version = 1.0.0
[ 62246.183] ABI class: X.Org Server Extension, version 10.0
[ 62246.183] (II) LoadModule: "intel"
[ 62246.183] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 62246.184] (II) Module intel: vendor="X.Org Foundation"
[ 62246.184] compiled for 1.20.11, module version = 2.99.917
[ 62246.184] Module class: X.Org Video Driver
[ 62246.184] ABI class: X.Org Video Driver, version 24.1
[ 62246.184] (II) LoadModule: "nvidia"
[ 62246.184] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 62246.184] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 62246.184] compiled for 1.6.99.901, module version = 1.0.0
[ 62246.184] Module class: X.Org Video Driver
[ 62246.184] (II) LoadModule: "intel"
[ 62246.184] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 62246.184] (II) Module intel: vendor="X.Org Foundation"
[ 62246.184] compiled for 1.20.11, module version = 2.99.917
[ 62246.184] Module class: X.Org Video Driver
[ 62246.184] ABI class: X.Org Video Driver, version 24.1
[ 62246.184] (II) UnloadModule: "intel"
[ 62246.184] (II) Unloading intel
[ 62246.184] (II) Failed to load module "intel" (already loaded, 0)
[ 62246.184] (II) LoadModule: "nvidia"
[ 62246.184] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 62246.184] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 62246.184] compiled for 1.6.99.901, module version = 1.0.0
[ 62246.184] Module class: X.Org Video Driver
[ 62246.184] (II) UnloadModule: "nvidia"
[ 62246.184] (II) Unloading nvidia
[ 62246.184] (II) Failed to load module "nvidia" (already loaded, 0)
[ 62246.184] (II) LoadModule: "libinput"
[ 62246.184] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 62246.185] (II) Module libinput: vendor="X.Org Foundation"
[ 62246.185] compiled for 1.20.8, module version = 0.30.0
[ 62246.185] Module class: X.Org XInput Driver
[ 62246.185] ABI class: X.Org XInput driver, version 24.1
[ 62246.185] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 62246.185] (II) intel: Driver for Intel(R) HD Graphics
[ 62246.185] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 62246.185] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 62246.185] (II) NVIDIA dlloader X Driver 470.223.02 Sat Oct 7 15:36:12 UTC 2023
[ 62246.185] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 62246.185] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20200917
[ 62246.185] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.917+git20200714-1+deb11u1 (Julien Cristau <jcristau@debian.org>)
[ 62246.185] (II) intel(0): SNA compiled for use with valgrind
[ 62246.204] (II) Loading sub module "fb"
[ 62246.204] (II) LoadModule: "fb"
[ 62246.205] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 62246.205] (II) Module fb: vendor="X.Org Foundation"
[ 62246.205] compiled for 1.20.11, module version = 1.0.0
[ 62246.205] ABI class: X.Org ANSI C Emulation, version 0.4
[ 62246.205] (II) Loading sub module "wfb"
[ 62246.205] (II) LoadModule: "wfb"
[ 62246.205] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 62246.205] (II) Module wfb: vendor="X.Org Foundation"
[ 62246.205] compiled for 1.20.11, module version = 1.0.0
[ 62246.205] ABI class: X.Org ANSI C Emulation, version 0.4
[ 62246.205] (II) Loading sub module "ramdac"
[ 62246.205] (II) LoadModule: "ramdac"
[ 62246.205] (II) Module "ramdac" already built-in
[ 62246.205] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics
[ 62246.205] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 6 threads
[ 62246.205] (==) intel(0): Depth 24, (--) framebuffer bpp 32
:
1. there is a lot of loading and unloading modules, which may also explain complained slowness . Can this be avoided?
2. How to get xrandr working ? xrandr conflicts with xinerama. But i need xinerama for both monitors at the moment.
I sold my car last week.
I have a public transport ticket and a bicycle and two legs still in good order.
At least here it is possible to have no car and still come around.
NO Car is better than ANY Car from the environmental view.
and Railway is better than Street traffic from the environmental view.
and no traffic is better than any traffic from the environmental view.
Use your choices.
Electric traction
has been around since 1879 on the railway with now only 20% of the energy consumption of the trucking industry.
Thanks
in the output of netstat -tulpen have these lines amongst others
netstat -tulpen | grep \-
Proto Recv-Q Send-Q Local Address Foreign Address State Benutzer Inode PID/Program name
tcp 0 0 0.0.0.0:42397 0.0.0.0:* LISTEN 0 1874 -
tcp 0 0 0.0.0.0:3142 0.0.0.0:* LISTEN 108 15793 1656/apt-cacher-ng
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 0 15825 -
tcp6 0 0 :::45827 :::* LISTEN 0 1877 -
tcp6 0 0 :::3142 :::* LISTEN 108 15794 1656/apt-cacher-ng
tcp6 0 0 :::2049 :::* LISTEN 0 15841 -
udp 0 0 0.0.0.0:57006 0.0.0.0:* 0 1873 -
udp6 0 0 :::49439 :::* 0 1875 -
I am wondering, what these lines are with the dash - at the end . Never seen this before.
Something to do with docker , which I recently installed?
so FB Groups is the only place to converse with other like minded people - in private groups, I hasten to add. wink
There are still people around who refuse to contribute to FB/instapound/wazzapp, and promote their refusal to those who invite to these groups
https://www.heise.de/news/systemd-255-B … 70784.html
oh oh oh :
SystemV-Skripte haben jetzt den Veraltet-Status (...) bekommen und werden künftig nicht mehr unterstützt.
==>
SystemV scripts have now been given the deprecated status (...) and will no longer be supported in the future.
I use dnsmasq and these blacklists/blocklists
https://github.com/notracking/hosts-blocklists
and my own blacklist . mostly FAGAM .
Also all sites, which refuse adblockers, will be added and not be accessed anymore.
This avoids a lot of traffic beginning with outgoing DNS inquiries. Saves time
(Ideologisch getriebene Distros wie z.B.Devuan mal außen vor gelassen).
de==> en
(Ideologically driven distros such as Devuan are left out)
If the systemd-sh*t would work flawlessly and transparent, nobody cared.
But it was a substantial and sensible deterioration of flawlessness, maintainability and transparency.
Saving Admin time seems to be ideology today.
Hi
Is it possible to delete a thread ?
I have opened a thread and described a proceeding which seem to not work anymore. see
https://dev1galaxy.org/viewtopic.php?id=5975
It would be wise, to delete the thread otherwise I have to edit and delete its contents by individual message
Sorry, This contained false information.
These instructions will work with devuan repos. Don't use any debian.org repos.
https://wiki.debian.org/QEMU
https://wiki.debian.org/VirtualBox
VirtualBox remains to ask for the non-free Oracle thing from the other website.
https://linuxize.com/post/how-to-instal … -on-debian
It remains qemu.
I installed xen-system-amd64 , but system became unbootable with dead displays. Deleted xen again.
Then I had to reinstall grub-efi-amd-64, which was deleted from the xen-install.
I keep on trying.
My internet service provider gives me a new ipv6 range /56 about every 8 weeks.
Then I stumble over this
ssh user@some other host
Warning: the ECDSA host key for ' some other host' differs from the key for the IP address '1111:2222:3333:4444:5555:6666:7777:8888'
Offending key for IP in /home/xx/.ssh/known_hosts:8
Matching host key in /home/xx/.ssh/known_hosts:11
Are you sure you want to continue connecting (yes/no)?
I do not want keys based on IPv6 . Each host in my intranet has a proper name chez moi.
That should be the identification for the keys
How can I suppress this seemingly automatic host key generation from varying references?
Windows viruses do not run in Wine
And you was looking over my shoulder.
And the earth is flat.
whoami
ps ax | grep -E "slim|lightdm"
set | grep -i display
echo $DESKTOP_SESSION
which firefox-esr
w
please run this code and paste the result to tell us more of your system
And if you run wine?
I have now scanned my home dir and uncovered a few infected applications hiding in wine.
Definitely worth using on Linux, as it is not as safe as it once was.
It is not the linux which is less safe, it is the w(h)ine install in your $HOME, which is unsafe.
Stop the wine application which offers all the uncertainties of windows.
Stick in an infected usb stick and wine will begin to work and distribute the virus inside your wine-home. I have seen this live on my Laptop.
I used to
apt remove wine*
and then have the directories scanned for viruses.
I Used antivir for that, still existing but it is no more in the distros I know
Have ever since 10 years not used any virus checking or w(h)ine anymore.
@chris2be8
I made an attempt to reinstall fail2ban on top of the still existing conf files.
apt install fail2ban
This failed and the system was borked as before.
now I looked for the /var/lib/dpkg/info/fail2ban.prerm script
changed the exit value to 0
dpkg --remove --force-remove-reinstreq fail2ban
(Reading database... 103543 files and directories are currently installed.)
Removing fail2ban (1.0.2-2)...
Stopping authentication failure monitor: fail2ban failed!
invoke-rc.d: initscript fail2ban, action stop failed.
Processing triggers for man-db (2.11.2-2)...
root@$HOSTNAME /var/lib/dpkg/info # dpkg --remove --force-remove-reinstreq fail2ban
dpkg: warning: request to delete fail2ban will be ignored, of which only the
conf files are on the system; use --purge to purge them
root@$HOSTNAME /var/lib/dpkg/info # dpkg --purge fail2ban
(Reading database... 103272 files and directories are currently installed.)
Deleting fail2ban (1.0.2-2) configuration files...
dpkg: warning: while removing fail2ban, directory '/usr/lib/python3/dist-packages/fail2ban/tests/files/config/apache-auth' is not empty, so will not be deleted
dpkg: warning: while removing fail2ban, directory '/usr/lib/python3/dist-packages/fail2ban/tests/files/action.d' is not empty, so it will not be deleted
dpkg: warning: while removing fail2ban, directory '/usr/lib/python3/dist-packages/fail2ban/tests/action_d' is not empty, so will not be deleted
dpkg: warning: while removing fail2ban, directory '/usr/lib/python3/dist-packages/fail2ban/server' is not empty, so will not be deleted
dpkg: warning: while removing fail2ban, directory '/usr/lib/python3/dist-packages/fail2ban/client' is not empty, so will not be deleted
dpkg: warning: while removing fail2ban, directory '/etc/fail2ban/jail.d' is not empty, so will not be deleted
dpkg: warning: while removing fail2ban, directory '/etc/fail2ban/filter.d' is not empty, so will not be deleted
dpkg: warning: while removing fail2ban, directory '/etc/fail2ban/action.d' is not empty, so will not be deleted
root@$HOSTNAME /var/lib/dpkg/info # rm -rf /etc/fail2ban
root@$HOSTNAME /var/lib/dpkg/info # rm -rf /usr/lib/python3/dist-packages/fail2ban
So Your advice worked. Thx
Finally got rid of the darn package which caused the highest load in the system.
I will do another thing to protect the server .
I need to speed up changes without breaking production platform(s).
Therefore I need to have a virtual machine for three purposes inside devuan chimaera
Run the already installed Win10 of this host for the purpose of updating my Navi from G????n. About every 4 weeks without necessarily restarting the computer.
copy the local distro installation and test the update / upgrade / dist-upgrade e.g. to daedalus for this machine
test a fresh install of daedalus for this machine
eventually upgrade to daedalus and stable and
continue to have an experimental playground for testing things.
A net search is dominated by results on running *n?x inside a win$ows environment OMFG and other commercial solutions.
this workstation failed badly on updating to daedalus. dpkg locked in on the non-free nvidia driver. It broke the distro upgrade and it needed a fresh install.
This took days. The Reinstall is described elsewhere here.
Therefore I am careful || wary || overcautious || paranoid , when tinkering on production systems. Select as appropriate.
I started now with installing various packages
dpkg -l | grep -E "xen|virt|kvm"
ii gir1.2-libvirt-glib-1.0:amd64 3.0.0-1 amd64 GObject introspection files for the libvirt-glib library
ii grub-xen 2.06-3~deb11u5 amd64 GRand Unified Bootloader, version 2 (Xen version)
ii grub-xen-bin 2.06-3~deb11u5 amd64 GRand Unified Bootloader, version 2 (Xen modules)
ii grub-xen-host 2.06-3~deb11u5 amd64 GRand Unified Bootloader, version 2 (Xen host version)
ii gvfs:amd64 1.46.2-1 amd64 userspace virtual filesystem - GIO module
ii gvfs-backends 1.46.2-1 amd64 userspace virtual filesystem - backends
ii gvfs-common 1.46.2-1 all userspace virtual filesystem - common data files
ii gvfs-daemons 1.46.2-1 amd64 userspace virtual filesystem - servers
ii gvfs-libs:amd64 1.46.2-1 amd64 userspace virtual filesystem - private libraries
ii libvirt-clients 7.0.0-3+devuan3 amd64 Programs for the libvirt library
ii libvirt-daemon 7.0.0-3+devuan3 amd64 Virtualization daemon
ii libvirt-daemon-config-network 7.0.0-3+devuan3 all Libvirt daemon configuration files (default network)
ii libvirt-daemon-config-nwfilter 7.0.0-3+devuan3 all Libvirt daemon configuration files (default network filters)
ii libvirt-daemon-driver-qemu 7.0.0-3+devuan3 amd64 Virtualization daemon QEMU connection driver
ii libvirt-daemon-driver-xen 7.0.0-3+devuan3 amd64 Virtualization daemon Xen connection driver
ii libvirt-daemon-system 7.0.0-3+devuan3 amd64 Libvirt daemon configuration files
ii libvirt-daemon-system-sysv 7.0.0-3+devuan3 all Libvirt daemon configuration files (sysv)
ii libvirt-glib-1.0-0:amd64 3.0.0-1 amd64 libvirt GLib and GObject mapping library
ii libvirt0:amd64 7.0.0-3+devuan3 amd64 library for interfacing with different virtualization systems
ii libxencall1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime library - libxencall
ii libxendevicemodel1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - libxendevicemodel
ii libxenevtchn1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - libxenevtchn
ii libxenforeignmemory1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - libxenforeignmemory
ii libxengnttab1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - libxengnttab
ii libxenhypfs1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime library - libxenhypfs
ii libxenmisc4.14:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - miscellaneous, versioned ABI
ii libxenstore3.0:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - libxenstore
ii libxentoolcore1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - libxentoolcore
ii libxentoollog1:amd64 4.14.5+94-ge49571868d-1 amd64 Xen runtime libraries - libxentoollog
ii python3-libvirt 7.0.0-2 amd64 libvirt Python 3 bindings
ii qemu-efi-aarch64 2020.11-2+deb11u1 all UEFI firmware for 64-bit ARM virtual machines
ii virt-manager 1:3.2.0-3 all desktop application for managing virtual machines
ii virtinst 1:3.2.0-3 all utilities to create and edit virtual machines
ii virtualbox-7.0 7.0.10-158379~Debian~bullseye amd64 Oracle VM VirtualBox
ii xen-doc 4.14.5+94-ge49571868d-1 amd64 XEN documentation
ii xen-hypervisor-4.14-amd64 4.14.5+94-ge49571868d-1 amd64 Xen Hypervisor on AMD64
ii xen-hypervisor-common 4.14.5+94-ge49571868d-1 all Xen Hypervisor - common files
ii xen-system-amd64 4.14.5+94-ge49571868d-1 amd64 Xen System on AMD64 (metapackage)
ii xen-tools 4.9-1 all Tools to manage Xen virtual servers
ii xen-utils-4.14 4.14.5+94-ge49571868d-1 amd64 XEN administrative tools
ii xen-utils-common 4.14.5+94-ge49571868d-1 amd64 Xen administrative tools - common files
ii xenstore-utils 4.14.5+94-ge49571868d-1 amd64 Xenstore command line utilities for Xen
What I did not like that one of the WWWsites wants me to install from oracle
ii virtualbox-7.0 7.0.10-158379~Debian~bullseye amd64 Oracle VM VirtualBox
Can it be done with the devuan packages only ?
It should be done with the devuan packages only.
a:
A metapackage would be appreciated which does the right thing.
b:
A How To for devuan should result from this thread.
whereas the Devuan ISO only has an MBR. Presumably it's the lack of GPT that makes the Devuan ISO non-bootable for your UEFI use case.
It's good you had an alternative method for installation.
I experienced the same problem but with a chimaera reinstall on an UEFI system. Before the upgrade to daedalus had catastrophically failed.
After reboot the system ended with a prompt of some sort (grub could not find a bootable partition). From there I managed to install the efi-grub and then could successfully start the chimaera again.
With the same USBStick I installed several old Laptops with BIOS.
The history of this problem seems to reach a bit more into history at least back to chimaera.
This fixed it
https://www.f1-consult.com/linux/debian … -packages/
Attention turn the music off! This is the last thing, I need, if I have to fix a problem.
Hi I had a rather smooth update/upgrade/dist-upgrade from chimaera to daedalus this night.
One package did not make it : fail2ban is now in a state where it cannot be removed, purged nor reinstalled
dpkg --force-conflicts --remove fail2ban > fail2ban_errors 2>&1
cat fail2ban_errors
(Reading database ... 73048 files and directories currently installed.)
Removing fail2ban (1.0.2-2) ...
Stopping Authentication failure monitor: fail2ban failed!
invoke-rc.d: initscript fail2ban, action "stop" failed.
dpkg: error processing package fail2ban (--remove):
installed fail2ban package pre-removal script subprocess returned error exit status 1
Starting Authentication failure monitor: fail2ban2023-09-02 14:21:41,881 fail2ban.configreader [13051]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'
2023-09-02 14:21:42,070 fail2ban [13051]: ERROR Failed during configuration: Bad value substitution: option 'ignorecommand' in section 'apache-fakegooglebot' contains an interpolation key 'ignorecommands_dir' which is not a valid option name. Raw value: '%(ignorecommands_dir)s/apache-fakegooglebot <ip>'
failed!
invoke-rc.d: initscript fail2ban, action "start" failed.
dpkg: error while cleaning up:
installed fail2ban package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
fail2ban
action "stop" failed.
This action must fail, because the fail2ban is not running from the beginning.
Stopping a not running process must not produce an error, because the wished result is already achieved. (initscripts?)
why does the removal procedure try to start the app ?
dpkg --force-remove-reinstreq --remove fail2ban
same result
locate fakegooglebot | grep -E "^/etc"
/etc/fail2ban/filter.d/apache-fakegooglebot.conf
/etc/fail2ban/filter.d/ignorecommands/apache-fakegooglebot
Nothing which I understand
Now I am lost, because this hinders other install activities . Each time dpkg is called, this errors show up, of course multiple times.
Due to the acquisition of a DP2DVI Adapter, this problem is no more existing in this form. to be continued in another thread