Posts by rolfie

rolfie · Other Issues

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

rolfie · Hardware & System Configuration

Instead of:

inukaze wrote:

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

rolfie · Desktop and Multimedia

Update:

Version 3.2.7-6 is in the repository now, fixes the issue.

Thanks, ROlf

rolfie · Hardware & System Configuration

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

rolfie · Hardware & System Configuration

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

rolfie · Hardware & System Configuration

Give the 4.19 kernel from backports a try.

Rolf

rolfie · Hardware & System Configuration

You might need some firmware. Try to install firmware-linux-free and firmware-linux-nonfree.

Regards, Rolf

rolfie · Hardware & System Configuration

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

rolfie · Desktop and Multimedia

@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.

rolfie · Desktop and Multimedia

@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

rolfie · Desktop and Multimedia

dxrobertson wrote:

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

rolfie · Desktop and Multimedia

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

rolfie · Desktop and Multimedia

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

rolfie · Desktop and Multimedia

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

rolfie · Installation

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

rolfie · Installation

stanz wrote:

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.

rolfie · Installation

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

rolfie · Installation

Under Linux use the UUID to address the drive/partition, do not use sdx. Then it does not matter if drives are detected in different order, renamed, exchanged....

I think Devuan ASCII does that automatically. Look up your fstab, if you see something like:

# /boot was on /dev/nvme0n1p2 during installation
UUID=6b1a5449-77ac-487b-b9e6-737ec8b8c677 /boot           ext4    defaults        0       2

for all your partitions you should be fine.

Regards, Rolf

rolfie · Installation

Got nearly 20 years of experience with running Windows in parallel to Linux, never saw something like this. Based on this I would recommend to closely look to the Windows side of things.

I am running ASCII amd64 with MATE on an UEFI board under 4.18 Kernel on a nvme ssd, and Win7 Prof 64bit on sda. Mate automatically pulls ntfs3g and exFAT as dependencies. Also put in an exFAT formatted USB stick sdf, the output from /proc/partitions looks like this:

# cat /proc/partitions
major minor  #blocks  name

 259        0  250059096 nvme0n1
 259        1     248832 nvme0n1p1
 259        2    1999872 nvme0n1p2
 259        3   64000000 nvme0n1p3
   8        0  488386584 sda
   8        1     261120 sda1
   8        2     131072 sda2
   8        3  274746368 sda3
   8        4  213245952 sda4
   8       16 1025600184 sdb
   8       17  958490624 sdb1
  11        0    1048575 sr0
   8       32 1953514584 sdc
   8       33 1953513472 sdc1
   8       64 3907018584 sde
   8       65 1953509376 sde1
   8       66  268435456 sde2
   8       67 1685071872 sde3
   8       48    7620288 sdd
   8       49    7616256 sdd1
 254        0   63997952 dm-0
 254        1   31997952 dm-1
 254        2   31997952 dm-2
 254        3  958488576 dm-3
 254        4 1953507328 dm-4
 254        5  977272832 dm-5
 254        6  976232448 dm-6
 254        7 1953511424 dm-7
 254        8 1685071616 dm-8
   8       80   30703616 sdf
   8       81   30699584 sdf1

No gaps in the display. The dm's are due to encryption.

32bit or 64bit should not matter, never had problems mixing them. ntfs filesystem is ntfs filesystem.

First of all run chkdsk on every Win7 drive including the C drive (requires a reboot and will be performed during startup). If that does not fix, obtain a gparted life cd suitable for your hardware, and check what gparted is reporting about your Win7 disk.

Good luck, Rolf

rolfie · Installation

Duke Nukem wrote:

BTW, the 100Mb sdb1 was created by Windows 7 for some purpose.

There is enough info in the net about this partition under Win7. It hosts the boot manager.

You seem to have an older PC with Bios or run your UEFI bios in CSM mode. Is this ASCII you are working with? What comes to my mind is that ntfs3g might be missing, though I would expect that it is installed automatically. Though this should not inhibit the display of the existing partitions.

What does blkid show?

Have you tried gparted?

Regards, Rolf

rolfie · Installation

Is there somewhere a hidden set of installation images of Beowulf around? Can't find anything in the official repositories. I tried an update on ASCII in a VM and got it busted, doesn't work. Would like to try a native installation, an alpha would be ok.

Thanks, Rolf

rolfie · Hardware & System Configuration

All current kernels have SMP enabled already since many years. Install it and you are done.

Regards, Rolf

rolfie · Other Issues

This is not related to Devuan itself, its about VBox 5.2.18 on ASCII and virtual machines in UEFI mode. Maybe somebody with experience has some hint.

The issue is that the machines do not start automatically, you have to manually enter fs0: cd /efi/distri grubx64 to get them up and running. VBox help wasn't enlightning, also found no hint in the net.

What can I do to make this work?

Thanks, Rolf

rolfie · Installation

I looked up my ASCII on a Ryzen 2700X platform with a NVME installation for Devuan and another SSD for Windows 7. Both installed in UEFI mode. I boot Devuan per default and get the choice in grub to boot Win7 if required.

I think you should create individual EFI partitions on the drives to have maximum decoupling.

Windows ignores other OSses. When you boot into Windows per default you normally have no choice. With some fiddling you may be able to boot other stuff from the Windows boot manager, but that can get screwed by updates. When I had a Debian and Windows7 on the same drive (without UEFI), I got some issues with Win7 updates that did not like grub in the MBR or even fail to update if Win isn't the only OS on the drive.

When you choose Devuan as default, run osprober (should run automatically actually), and this will enter Win10 into the grub menu, so you can select at boot time into which OS to boot. No issues with this setup.

My EFI Bios has the option to override the default an select from a menu which OS I want to boot.

Regards, rolfie

rolfie · Other Issues

There are pro and cons for both.

I used the entry in the sources.list at first, then got that this can be risky if there are package updates from Oracle that may conflict with the Debian/Devuan stuff. Then had the entry active only for the install, and got tired of commenting it out when I learned that I can also simply install the package with dpkg -i, and I use it since. Good enough for my small private environment.

Your choice.

Regards, Rolf

The officially official Devuan Forum!

#1176 Re: Other Issues » Beowulf - Policykit » 2019-02-09 21:02:51

#1177 Re: Hardware & System Configuration » [SOLVED]I had upgrade Jessie to Ascii and i need some fixes.[SOLVED] » 2019-02-09 20:01:34

#1178 Re: Desktop and Multimedia » [Solved] Mate and lightdm on Beowulf » 2019-02-09 16:18:22

#1179 Re: Hardware & System Configuration » root-Terminal on Beowulf » 2019-02-09 16:12:56

#1180 Re: Hardware & System Configuration » root-Terminal on Beowulf » 2019-02-09 15:28:45

#1181 Re: Hardware & System Configuration » [SOLVED] wlan0 interface not recognized by `ifconfig' nor `ip link' » 2019-02-09 11:44:53

#1182 Re: Hardware & System Configuration » [SOLVED] wlan0 interface not recognized by `ifconfig' nor `ip link' » 2019-02-08 21:42:59

#1183 Hardware & System Configuration » root-Terminal on Beowulf » 2019-02-08 21:19:49

#1184 Re: Desktop and Multimedia » [Solved] Mate and lightdm on Beowulf » 2019-02-08 17:39:07

#1185 Re: Desktop and Multimedia » [Solved] Mate and lightdm on Beowulf » 2019-02-08 16:17:39

#1186 Re: Desktop and Multimedia » [Solved] Mate and lightdm on Beowulf » 2019-02-08 15:36:35

#1187 Re: Desktop and Multimedia » [Solved] Mate and lightdm on Beowulf » 2019-02-08 12:27:07

#1188 Re: Desktop and Multimedia » [Solved] Mate and lightdm on Beowulf » 2019-02-08 09:57:28

#1189 Desktop and Multimedia » [Solved] Mate and lightdm on Beowulf » 2019-02-07 20:04:56

#1190 Re: Installation » [Solved] Beowulf installation image » 2019-02-07 16:31:38

#1191 Re: Installation » [Solved] Beowulf installation image » 2019-02-07 10:42:49

#1192 Re: Installation » [Solved] Beowulf installation image » 2019-02-06 15:27:48

#1193 Re: Installation » Dual-boot with Windows 10 from separate drives » 2019-02-06 15:02:20

#1194 Re: Installation » NTFS Partitions not recognised » 2019-02-06 13:40:41

#1195 Re: Installation » NTFS Partitions not recognised » 2019-02-04 19:38:51

#1196 Installation » [Solved] Beowulf installation image » 2019-02-03 20:57:44

#1197 Re: Hardware & System Configuration » [SOLVED] Ascii kernel for SMP (DELL T430 dual cpu) » 2019-02-03 16:01:17

#1198 Other Issues » Advice on VBox machine in UEFI mode » 2019-02-02 19:01:07

#1199 Re: Installation » Dual-boot with Windows 10 from separate drives » 2019-01-30 19:28:27

#1200 Re: Other Issues » Devuan as VirtualBox host system » 2019-01-24 20:58:17

Board footer