You are not logged in.
Thanks for the feedback, still no step further. I can't get along with the grub command line. I have looked at some stuff from Ubuntuusers, that was of limited use. I learned how to navigate in the uefi shell, but grub is sealed for me.
Booted my favorite life system Knoppix, and could not find any grub-efi-amd64-signed file wherever. grub-install in efi mode was noit possible since Knoppix does not boot in efi mode. Maybe I have to download an ASCII or Stretch life system.
Thanks, Rolf
Note: tried in a VBox: no encryption, efi with sysvinit and open-rc, both end in the grub command line. The efi installer is broken.
Are you using VBox from the Devuan repository or the Oracle version?
In any case, make sure you have build-essential, dkms and the headers for your kernel installed. Then missing modules should be no problem.
Good luck, Rolf
After successfully installing native Beowulf in a VM, I thought I might give Beowulf a try on my secondary PC. Now I am facing some problems: after reboot I end up in the grub shell. When I enter boot grub tells me the kernel is not loaded.
Boundary conditions: EFI mode, amd64, installation from USB stick, system encrypted. The VM had no EFI, was installed from the iso directly, no encryption.
Tried to fix with the rescue mode: reinstalled grub, went into shell with the encrypted root, update-grub from there, update-initramfs from there, no change. Also burned the iso on a CD and tried again, no help. Isn't the shell offered a fully working chroot environment?
I am no sure if there is an issue with the netinstall iso, or if my detours have contributed (initially I had some other drives and an USB card reader connected, so the SSD for Beowulf was sdi).
Is there a way to fix the installation?
Thanks, Rolf
No, no policykit-1-gnome installed. I got policykit-1, mate-polkit and mate-polkit-common installed.
These are the suttle differences....
Regards, Rolf
Sorry, there are some things different on xfce compared to Mate.
Good luck, Rolf
What synaptic is concerned, the menu entry in Mate is synaptic-pkexec.
There is a shell skript in /usr/bin:
#!/bin/sh
pkexec "/usr/sbin/synaptic" "$@"
The policy looks ok to me. Maybe its worth to check the path settings?
Regards, Rolf
Same versions as in my VM where synaptic works.
Check in /usr/share/polkit-1/actions if you got a file named com.ubuntu.pkexec.synaptic.policy in there.
Rolf
Give us an idea how polkit is looking like:
apt list --installed policykit*
apt list --installed libpolkit*
Regards, Rolf
My Beowulf netinstall VM with lightdm/Mate works, no issues related to the policykit. i.e. I can call synaptic, work with USB on Mate, shutdown/reboot from Mate and lightdm.
Thanks, Rolf
Instead of:
The content of /etc/udev/rules.d/20-mm-blacklist-mtk.rules right now is :
ATTRS{vendor}=="0e8d", ENV{ID_MM_DEV ICE_IGNORE}="1" ATTRS{vendor}=="6000", ENV{ID_MM_DEV ICE_IGNORE}="1"
use:
ATTRS{vendor}=="0e8d", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{vendor}=="6000", ENV{ID_MM_DEVICE_IGNORE}="1"
See the difference? Udev is not exactly pointing to the error, its just complaining that its failing.
Regards, Rolf
Update:
Version 3.2.7-6 is in the repository now, fixes the issue.
Thanks, ROlf
Update: after adding a policy-file, mate-terminal as root is opened. Geany can be used.
Question remains if this is a good path setting for a root terminal?
echo $PATH
/usr/sbin:/usr/bin:/sbin:/bin:/root/bin
Next step: see how mate-system-log is doing.
Update: works after adding another policy.
Thanks, Rolf
I have looked at the thread, and analysed what I have here.
The policykit stuff I have is version 0.105-25, seems to be complete. As authentification agent the package polkit-mate-authentication-agent-1 is installed.
# apt list policykit* --installed
Auflistung... Fertig
policykit-1/testing,now 0.105-25+devuan1 amd64 [Installiert,automatisch]
# apt list libpolkit* --installed
Auflistung... Fertig
libpolkit-agent-1-0/testing,now 0.105-25+devuan1 amd64 [Installiert,automatisch]
libpolkit-backend-1-0/testing,now 0.105-25+devuan1 all [Installiert,automatisch]
libpolkit-backend-elogind-1-0/testing,now 0.105-25+devuan1 amd64 [Installiert,automatisch]
libpolkit-gobject-1-0/testing,now 0.105-25+devuan1 all [Installiert,automatisch]
libpolkit-gobject-elogind-1-0/testing,now 0.105-25+devuan1 amd64 [Installiert,automatisch]
Maybe I need to give the version 0.105-18 a try. Other ideas?
Thanks, Rolf
Give the 4.19 kernel from backports a try.
Rolf
You might need some firmware. Try to install firmware-linux-free and firmware-linux-nonfree.
Regards, Rolf
My VM with Beowulf amd64/Mate/lightdm/elogind is working now.
What I am missing is a way to create a direct menu path to a root terminal as I had up to ASCII. Was simply done by creating a new menu entry with the command line gksu mate-terminal. Now gksu has been dropped. What would be the replacement? I tried with pkexec mate-terminal instead, am asked to enter the root-PW and nothing else happens.
I consider opening a user terminal and to use su - instead just as a workaround. su has a srewed default path and is unusable.
Suggestions?
Thanks, Rolf
@xinomilo: thanks for the tip to use a Live CD to download the files directly to a folder in the VM, that really helped. The downgrade works, I can use the VM now.
A try to get
apt install eudev=3.2.7-3
working failed, a USB stick was not recognised from the rescue mode as device, I could not mount it.
I think I need to pin this version for the time until a fix is around, don't I?
Thank your for your contributions, Rolf
PS: when I first tried ASCII/Mate/lightdm about a year ago, I used consolekit because I was used to it and had issues like no shutdown, no automount of USB devices, no access to synaptic. All gone when using elogind. There are some threads in here with my contributions.
@Golinux: I don't like slim at all. Got 3 ASCII PCs up and running with lightdm/Mate/elogind with the help of this forum. I expect Beowulf to be the same.
@xinomilo: bugs 290/111 describe what I see here. I will give an earlier version of eudev a try if I manage to get it installed.
Thanks, Rolf
Do you have a symlink in /etc/alternatives/lightdm-greeter that points to /usr/share/xgreeters/lightdm-gtk-greeter.desktop?
As far as getting to a console, can you <CTRL><ALT>F2 to get to a terminal console? Then it would be <CTRL><ALT>F7 to get back to gui/lightdm.
Is desktop-base installed?
The symlink is there and points to the same location.
desktop-base is installed, version 10.0.0 testing.
<CTRL><ALT>F2 brings me to a console on my workstation (ASCII), <ALT>F2 causes no reaction on the VM. It looks to me as if the keyboard is dead.
Thanks, Rolf
Have no chance to get to a console either. I can boot Knoppix as Live system into this VM and chroot to check what is installed, install with apt ....
Here are some logs:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=1809
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Monitoring logind for seats
[+0.02s] DEBUG: New seat added from logind: seat0
[+0.02s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.02s] DEBUG: Seat seat0: Starting
[+0.02s] DEBUG: Seat seat0: Creating greeter session
[+0.02s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: posix_spawn avoided (fd close requested)
[+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.02s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.02s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.02s] DEBUG: XServer 0: Launching X Server
[+0.02s] DEBUG: Launching process 1821: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.09s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.09s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.11s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested)
[+0.29s] DEBUG: Got signal 10 from process 1821
[+0.29s] DEBUG: XServer 0: Got signal from X server :0
[+0.29s] DEBUG: XServer 0: Connecting to XServer :0
[+0.29s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified)
[+0.29s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.29s] DEBUG: Session pid=1893: Started with service 'lightdm-greeter', username 'lightdm'
[+0.30s] DEBUG: Session pid=1893: Authentication complete with return value 0: Success
[+0.30s] DEBUG: Seat seat0: Session authenticated, running command
[+0.30s] DEBUG: Session pid=1893: Running command /usr/sbin/lightdm-gtk-greeter
[+0.30s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+0.30s] DEBUG: Session pid=1893: Logging to /var/log/lightdm/seat0-greeter.log
[+0.30s] DEBUG: Activating VT 7
[+0.42s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false
[+0.59s] DEBUG: Greeter start authentication
[+0.59s] DEBUG: Session pid=1925: Started with service 'lightdm', username '(null)'
[+0.61s] DEBUG: Session pid=1925: Got 1 message(s) from PAM
[+0.61s] DEBUG: Prompt greeter with 1 message(s)
cat seat0-greeter.log
** (process:1893): WARNING **: 12:57:34.553: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
** Message: 12:57:34.574: Starting lightdm-gtk-greeter 2.0.6 (Dec 27 2018, 16:15:47)
** Message: 12:57:34.576: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf
** Message: 12:57:34.576: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
** (lightdm-gtk-greeter:1899): WARNING **: 12:57:34.699: [PIDs] Failed to execute command: upstart
(lightdm-gtk-greeter:1899): Gtk-WARNING **: 12:57:35.049: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)
(lightdm-gtk-greeter:1899): Gtk-WARNING **: 12:58:00.787: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)
(lightdm-gtk-greeter:1899): Gtk-WARNING **: 12:59:00.856: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)
(lightdm-gtk-greeter:1899): Gtk-WARNING **: 13:00:00.920: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)
In here is a complant that consolekit is missing. Can this be the reason? elogind is installed.
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
Current Operating System: Linux rh055 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-2-amd64 root=UUID=0aab8de5-7fa6-4847-87a3-de5caf7539d6 ro quiet
Build Date: 25 October 2018 06:15:23PM
xorg-server 2:1.20.3-1 (https://www.debian.org/support)
Current version of pixman: 0.36.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 8 12:57:34 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
error setting MTRR (base = 0x00000000e0000000, size = 0x03000000, type = 1) No such device or address (6)
Anything in there that catches somebodies eyes?
Thanks, Rolf
Is installed, version 2.0.6-1. lightdm is version 1.26.0-3.
Tried to add lightdm-gtk-greeter-settings, does not make a difference.
Thanks, Rolf
Got Beowulf installed from the just rebuilt netinstall iso. Just went as far the get the command line working, no desktop. No issues, this
worked perfectly. Used openrc. All in VBox, guest and host amd64, host and guest extensions are installed.
Then manually installed xorg, lightdm and mate-desktop-environment-extra. No errors from apt. When I reboot, I get the lightdm loginscreen, but there is no way to enter username/password, nor can I access any of the icons present in the top panel. No reaction at all.
What is wrong here?
There is an error during boot from eudev, needs service unmountroot (I hope this is correct, the output scrolls very fast and CRTL-S does not work). Is this the key? What do I need to install or re-configure?
Thank you for your feedback, Rolf
Thanks, that rebuilt works, got a working Beowulf CLI interface.
Tried to manually setup my Mate with lightdm, there I am stuck, can't enter username/password during login. Different topic though.
Thanks, Rolf
Greetings All...
No kernel modules found. Using ca & us mirrors.
No disk drives found. Aborted attempt for now, since I can't get passed that!
Same with me, German mirror, non EFI expert install, tried all 3 offered distribtions ASCII, Beowulf, Ceres, all the same.
Regards, Rolf
Addendum: also the image dated April 18 shows the same kernel modules error.
Thanks for the link, I'll give it a try. Is it correct that the image is dated something like April 18?
Apart from that the further discussion left me behind. Too may acronyms like XD, ML, YMMV, ATM.
Well, meanwhile used the duck to look up what that means and got the explanations now, but the first reading was just causing ?????
Regards, Rolf