You are not logged in.
I have now removed the xserver-xorg-video-intel package, which made no difference, either with or without /etc/X11/xorg.conf.d/00-modesetting.conf.
EDIT: is there anything printed in the X.Org log when you experience the problem?
There is a lot of stuff in the Xorg.0.log file and I can't see anything which tells me anything helpful. I will carry on looking at the xserver-xorg-video-intel package.
Thank you for your suggestions.
I have created the file /etc/X11/xorg.conf.d/00-modesetting.conf, as suggested in your indicated posting, containing :-
Section "Device"
Identifier "Intel Graphics"
Driver "modesetting"
EndSection
And rebooted into the 5.10 kernel, but the cursor problem is still there.
I notice that the word modesetting is used. This may be related to the problem I was trying to investigate! This was that dmesg reports :-
broken atomic modeset userspace detected, disabling atomic
This occurs with both kernels. I don't know whether it is a red herring!
Geoff
I was investigating an error message (unrelated to the cursor) when I installed the backports kernel. This did not fix the unrelated problem, but it did produce an odd effect on the cursor.
I was running Beowulf with the 4.19.0-12 kernel and then installed 5.10.0-0.bpo.3-amd64.
I am using LXQt, with Openbox.
On Intel hardware and graphics.
With the backports kernel, the cursor is very slow to change as I move over different areas. Thus, as I move over the corner of a window, it can take 4 or 5 seconds for the cursor to complete the change from an arrow to the L shaped corner drag cursor. This does not happen on the 4.19 kernel.
I have had a quick search and have not found any references to this behaviour. Does this mean anything to anyone?
Geoff
I have a separate partition on my SSD for /boot with further partitions under LVM for / and /home.
Then on my HDD I have a partition for swap with further partitions under LVM for /var as well as my VMs which run under Xen.
The idea was to have the potentially rapidly changing stuff on the HDD, but boot quickly off the SSD. It seemed like a good idea at the time ;-)
[ also looking at the other thread https://dev1galaxy.org/viewtopic.php?id=3628&p=2 ]
The getty-run package ships with a getty-S0 on serial that is disabled by default. Enabling it is usually enough for other virtualization environment like Qemu or Docker, but I've never run Xen so I don't know.. is the getty on hvc0 a requirement for Xen, or anyway a commonly required feature?
If that is the case I can ship a getty on hvc0 too so that the only thing left to do is to enable it.
Let me know!
I would not claim to be an expert on Xen, but I do believe that it is necessary to get hvc0 working in order to be able to log in when running Paravirtualised
https://wiki.xenproject.org/wiki/Xen_Co … ms#Console
So, your suggestion sounds good to me.
Geoff
Are you using runit under SysVinit or are you using runit-init. With the latter you need to do some setting up of getty. When I do that in a VM under Xen, I have to set up a getty on hvc0 for the console.
Geoff
Does top show anything grabbing lots of cpu or memory?
Remember, if it ain't Baroque don't fix it.
So, if you like Vivaldi's 4 Seasons, then you could try this version of the Storm sequence from Summer, played by the Ukranian group B&B Project, (Bandorla and Button Accordian)
https://www.youtube.com/watch?v=UYW7mrY8Dg0
If that went down well you could also try their version of Bach's Toccata and Fugue in D minor (BWV 565).
https://www.youtube.com/watch?v=DrJY_-BIasY
Geoff
Having reported some problems with shutdown, I have just discovered that the version supplied with runit-init does work, but with no arguments!
shutdown
Actually, I think you can simplify the log/run file further :-
#!/bin/sh
NAME=postgresql
LOG="/var/log/runit/$NAME"
install -o _runit-log -g adm -d $LOG
exec chpst -u _runit-log svlogd -tt "$LOG"
Geoff
In fact
update-service --add /etc/sv/postgresql
also sets up the supervise subdirectories, as necessary. This command does not set up the log file, however, the log/run file which fsmithred presents, above, is very good as it sorts out the log file and only requires the setting up of the service name. If you use the above command and the log/run file, which I have copied here, then this makes the setting up process pretty straightforward.
#!/bin/sh
NAME=postgresql
LOG="/var/log/runit/$NAME"
test -d "$LOG" || mkdir "$LOG" && chown -R _runit-log:adm "$LOG"
exec chpst -u _runit-log svlogd -tt "$LOG"
Geoff
edited <service> to be the same in both examples
I also use Palemoon. I have this forum permanently open in a tab, but only log in as required and have just logged in to post this.
Geoff
It took a few goes and a few reads of the man page to get it to work, but it seems that the <service> part of the command requires the directory which you have set up. Thus the command I actually gave was :-
update-service --add /etc/sv/postfix
This seems to set it up nicely.
- add the service with update-service --add <service>
Ah! Thank you for that. I thought that there should be a command to add in a new service rather than just putting in a link manually, but I had not come across it. I see from the man page that it does some checking, which is good.
On a fresh install of Chimaera in a VM under Xen,
https://dev1galaxy.org/viewtopic.php?pid=27870#p27870
I tried switching to runit-init.
apt install runit-init
It was still running with the old init so I wanted to reboot it. From Dom0 I tried to shutdown via Xen
xl shutdown chimaera
which had no effect, so I hit it with a bigger hammer
xl destroy chimaera
which did stop it!
On booting it again it recovered the disk from the journal, but did come up.
It gave no login prompt, which was due to my not having set up the virtual console for Xen, hvc0.
However, reconnecting to Chimaera via ssh and VNC worked as normal.
The only services running under runsvdir are getty and ssh.
To set up hvc0 as the console, I copied the set up for tty1.
cd /etc/sv/
cp -rp getty-tty1/ getty-hvc0
cd getty-hvc0
edit run and finish to change tty1 to hvc0
rm supervise
ln -s /run/runit/supervise/getty-hvc0 supervise
cd /etc/sv
runsv getty-hvc0
This does not return, which I believe is correct, and the login prompt now appears on the console (the window on Dom0)
To set it up to work automatically needs it linked in to /etc/service
cd /etc/service
ln -s /etc/sv/getty-hvc0/ .
The other glitch is shutting it down.
Using LXQt to shutdown closes the LXQt window but I was still logged in on the console.
shutdown -hH now
did not shut it down.
Coming back to Dom0 I was able to give the command to Xen to shut it down
xl shutdown chimeara
which did work.
Having booted it up again, I was able to shut down with
init 0
I noticed that /sbin/shutdown is a link to /lib/runit/shutdown
Geoff
Chimaera fresh install via debootstrap
I wanted to do a fresh install of Chimaera from my Beowulf set up and used the debootstrap method to do it. The installation went very smoothly, apart from errors on my part, which I have edited out!
/etc/xen-tools/xen-tools.conf is well commented. The options, which I have set, look like this :-
# grep -v '^#' xen-tools.conf | grep '.'
lvm = HDD0 # set the name of your lvm volume group here
install-method = debootstrap
debootstrap-cmd = /usr/sbin/debootstrap
size = 20G # Root disk, suffix (G, M, k) required
memory = 2G # Suffix (G, M, k) required
swap = 4G # Suffix (G, M, k) required
fs = ext4 # Default file system for any disk
# Default distribution is determined by Dom0's distribution
dist = chimaera
image = sparse # Specify sparse vs. full disk images (file based images only)
gateway = 192.168.2.1
netmask = 255.255.255.0
broadcast = 192.168.2.255
dhcp = 1
nameserver = 192.168.2.1
bridge = xenbr0
cache = no
genpass = 0
passwd = 1
accounts = 0
kernel = /boot/vmlinuz-`uname -r`
initrd = /boot/initrd.img-`uname -r`
pygrub = 1
arch = amd64
mirror = http://deb.devuan.org/merged
ext4_options = noatime,nodiratime,errors=remount-ro
ext3_options = noatime,nodiratime,errors=remount-ro
ext2_options = noatime,nodiratime,errors=remount-ro
xfs_options = defaults
reiserfs_options = defaults
btrfs_options = defaults
copyhosts = 1
Now need to add chimaera to the known suites.
If you have not done this before, then you need to set up devuan.d in /usr/share/xen-tools, see
https://dev1galaxy.org/viewtopic.php?pid=13368#p13368
but you will now need to add chimaera :-
cd /usr/share/xen-tools
ln -s devuan.d chimaera.d
I think this is a new step for debootstrap :-
cd /usr/share/debootstrap/scripts
ln -s ceres chimaera
The configuration should now be ok, so get on and install it!
cd /etc/xen
xen-create-image --hostname chimaera
This took about 6 minutes to install chimeara.
lvs includes the info :-
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
...
chimaera-disk HDD0 -wi-a----- 20.00g
chimaera-swap HDD0 -wi-a----- 4.00g
...
And the file /etc/xen/chimaera.cfg has been created. The new VM can now be booted.
cd /etc/xen
xl create chimaera.cfg ; xl console chimaera
Which boots nicely to the login prompt. Log in as root.
apt update
apt full-upgrade
This had nothing to do, although it could not find chimaera-security, un-surprisingly!
When I tried, it was not able to install vnc4server or gksu. The later is to be expected.
vnc4server has been replaced by tigervnc-standalone-server.
apt install task-lxqt-desktop synaptic tigervnc-standalone-server
Need to answer the questions to configure the keyboard.
Then install some of my favourite things.
apt install task-british-desktop rxvt-unicode claws-mail xauth
And set up a user
addgroup --gid 1026 user1
adduser --uid 1026 --gid 1026 user1
su - user1
mkdir .vnc
cd .vnc
cat << 'EOF' >> vnc.conf
# This file, $(HOME)/.vnc/vnc.conf will be sourced after /etc/vnc.conf,
# so values can be
# overwritten on a per-user basis. If you want to reactivate the default
# value here, you have to specify an undef value. For example, $fontPath
# will set to the default value after
#
# $fontPath = "/foo";
# $fontPath = undef;
# set up the screen size which you would like
$geometry = "1900x1200";
# Tell vncserver to accept connections from addresses other than localhost
$localhost = "no";
EOF
In an earlier version, above, I failed to quote the 'EOF' after cat, which does not pass through the variables! Unfortunately I am unable to go back and edit it.
Start up the VNC server as the user.
vncserver
You will have to enter a new VNC password.
back on Dom0 as the user
vncviewer chimaera:1
You will have to enter the VNC password and your new session should display.
Use synaptic to install openbox and select it in the LXQt Session Settings preferences, if that is what you would like.
The file system looks like this :-
df -h
Filesystem Size Used Avail Use% Mounted on
udev 940M 0 940M 0% /dev
tmpfs 198M 112K 198M 1% /run
/dev/xvda2 20G 4.0G 15G 22% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.2G 0 1.2G 0% /dev/shm
tmpfs 198M 8.0K 198M 1% /run/user/1026
To use chimeara normally, as user on Dom0
ssh -L 5901:localhost:5901 chimaera
on chimeara
vncserver
as user on Dom0 in another window
vncviewer :1
give the password and there it is!
I have tried runit as a supervisor under SysVinit and under OpenRC and reported what I did to get various services supervised by runit at :-
https://dev1galaxy.org/viewtopic.php?id=1748
The part about Postfix rambles on a bit and eventually I got a much simpler set-up for it, which is included at the above link.
There are some further links including OpenRC at :-
https://dev1galaxy.org/viewtopic.php?pid=23816#p23816
Geoff
Have you tried turning on logging in OpenRC?
In /etc/rc.conf you may find a line :-
#rc_logger="NO"
change that to
rc_logger="YES"
and you should get the logging as OpenRC does its stuff, in /var/log/rc.log, although the location can also be changed in /etc/rc.conf.
Also the command rc-status should show you what state each service is in.
Geoff
I notice at the above links to github, that v 246 is being worked on and that there have been a lot of commits today, 8 Nov 2020.
If you have 2 cards sharing the same module, use the enable option. See :-
https://dev1galaxy.org/viewtopic.php?pid=23900#p23900
Geoff
I have just updated my laptop running chimaera and it holds back Wireshark on version 3.2.5-1 rather than upgrading to 3.2.6-1.
As far as I can see, this is because Wireshark has a dependency on libsystemd0. I think it is wireshark-common that actually has the dependency.
Geoff
There is a discussion about which email client to use :-
https://dev1galaxy.org/viewtopic.php?id=3119
Geoff
The first few posts in the thread "Xen and the art of VM" describe using debootstrap to install an image.
https://dev1galaxy.org/viewtopic.php?id=2556
The thread then goes off describing how to try out other ways of installing, if you want to look at installers!
I hope that the first few posts are still relevant.
Geoff
Those instructions were written around five years ago. One thing which I spotted is that the mirror should probably be updated from :-
mirror = http://packages.devuan.org/merged
to:-
mirror = http://deb.devuan.org/merged
Geoff