Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1

#1 Re: Installation » [SOLVED] Chimaera Dual Boot with Existing Windows (GPT/EFI): No GRUB Menu » 2022-07-26 08:24:59

giorgiob
Head_on_a_Stick wrote:

If /sys/firmware/efi/ does not exist then the system is not booted in UEFI mode and no new NVRAM boot entries can be made.

@OP: make sure "Legacy" mode (CSM) is disabled and UEFI is enabled in the firmware ("BIOS") options.

As a last resort Windows can chainload Devuan with this command (run as Administrator):

bcdedit /set "{bootmgr}" path "\EFI\debian\grubx64.efi"

That was the problem! I have enabled both legacy and UEFI in the BIOS, and legacy had higher priority so the installation USB stick was booted in legacy mode.
After changing the priority, I started the USB-stick in recovery mode and the efi directory was there. However, efivars had not been mounted and I had to mount it by hand. After that

# update-grub
# grub-install --target=x86_64-efi

did the job: I now get the GRUB menu with Devuan as default entry and from there I can also boot into Windows.

Thanks a lot for all the answers!

#2 Re: Installation » [SOLVED] Chimaera Dual Boot with Existing Windows (GPT/EFI): No GRUB Menu » 2022-07-25 21:02:30

giorgiob

Thanks a lot for the hints.

I have booted into recovery mode: There is indeed no directory /sys/firmare/efi, neither in the installer console nor in the chroot shell.
I tried

# mount -t efivarfs efivarfs /sys/firmware/efi/efivars

In the chroot shell this gives:

mount: /sys/firmware/efi/efivars: mount point does not exist

I am not allowed to create the mount point:

# mkdir -p /sys/firmware/efi/efivars
mkdir: cannot create directory `/sys/firmware/efi': Operation not permitted

Trying to mount from another console (without chroot) gives the following error:

mount: mounting efivarfs on /sys/firmware/efi/efivars failed: No such file or directory

#3 Installation » [SOLVED] Chimaera Dual Boot with Existing Windows (GPT/EFI): No GRUB Menu » 2022-07-25 19:10:28

giorgiob
Replies: 6

I am trying to install Devuan Chimaera on a Lenovo ThinkPad that has Windows 10 pre-installed.
I would like to have a dual boot system. I have done such installations many times with MBR but
I have no experience with EFI/GPT.

The SSD internal disk has a GPT-partitioning that initially looked like this:

/dev/sda1 1G Microsoft basic data
/dev/sda2 260M EFI System
/dev/sda3 500M Microsoft reserved
/dev/sda4 ~220 G Microsoft basic data (drive C:)
/dev/sda5 953 M Microsoft basic data

I have shrinked partition 4 from Windows and then installed Devuan using a netinstall image.
From the installer, I have created a 1G ext4 boot partition (/dev/sda6) and a 124 G encrypted partition (/dev/sda7) in the free space.
Then I have used the encrypted partition as a volume for LVM and put a swap and a root partition in it.

The installation seemed to work. I had a warning from GRUB but I thought everything would be OK.
But when I rebooted the laptop I got not GRUB-menu: the system just booted into Windows.

So I read some domentation (https://www.gnu.org/software/grub/manual/grub/grub.html, Section 4.1 Installing GRUB using grub-install)
and I rebooted the installation USB-stick into recovery mode and opened a shell in the root filesystem of the installation.

There; I followed the instructions from the GRUB documentation and made a directory

/boot/efi

and mounted the EFI System partition (/dev/sda2) under /boot/efi. Then I ran

# update-grub
# grub-install --target=x86_64-efi

This seemed to work, even though the second command printed a warning: EFI variables are not supported on this system.
Anyway, the EFI System partition now contained a directory:

/EFI/debian

or

/boot/efi//EFI/debian

from Devuan.

So, I left the recovery shell and rebooted but I still got no GRUB-menu: The computer booted directly into Windows as if GRUB were not installed.

Do you have any hints? I can reinstall from scratch and post any GRUB warnings here in case you need more detailed information.

#4 Installation » Merging several configuration files after upgrade to beowulf » 2021-03-31 08:42:11

giorgiob
Replies: 1

I have just upgraded my laptop from ascii to beowulf by following the documentation at https://www.devuan.org/os/documentation … to-beowulf. Everything went smoothly, except for a few minor glitches, which I summarize below.

During the upgrade of the tor package, I had a warning that the installed configuration file /etc/tor/torrc has been changed locally. I chose not to overwrite the local file and to merge the new file afterwards. I was left with my original torrc file and an additional /etc/tor/torrc.dpkg-dist file. What surprised me was the following:
- The version of the installed tor package is 0.3.5.14-1
- The header of my old torrc file contains the text
   Last updated 22 September 2015 for Tor 0.2.7.3-alpha.
- The header of the new torrc.dpkg-dist file contains:
   Last updated 9 October 2013 for Tor 0.2.5.2-alpha.

So neither of the configuration files is up to date with the installed package version, and the configuration suggested by the installed package is older than the previous configuration. I am not sure what to do: just keep my old configuration file?

I have a similar problem with package lvm2: I had a configuration conflict during dist-upgrade and delayed the upgrade (kept my configuration file). While merging the new file /etc/lvm/lvm.conf.dpkg-dist with the old file /etc/lvm/lvm.conf, I noticed the following:
- The only thing I had changed was setting use_lvmetad = 0 This was due
   to some warning I got during boot.
- In the new configuration file this variable is missing completely.
Has this variable been removed from the lvm configuration / is it safe to remove it from my configuration file?

Last thing that occurred to me is the following: during shutdown I used to have some console logging output of various steps being performed, similar to the logging that is shown during system startup. After upgrading to beowulf the startup logging is still there but there is no shutdown logging: the screen turns black for a few seconds and then the laptop is switched off. Has some configuration been changed automatically? How can I restore the shutdown logging output?

#5 Re: Installation » Migration ascii -> beowulf. Mate Shut Down disappeared » 2020-09-11 14:46:52

giorgiob

Thanks a lot. elogind had indeed not been installed. I do not know exactly why and I hadn't noticed any error during the dist-upgrade. I have installed it not (it had to remove consolekit, if I remember correctly) and now the shutdown function is back.

#6 Installation » Migration ascii -> beowulf. Mate Shut Down disappeared » 2020-09-09 15:32:05

giorgiob
Replies: 3

One week ago I migrated my work laptop from Devuan ascii to beowulf. Everything seemed to go fine but when I logged in into my mate desktop I realised that the meny entry System -> Shut Down was gone. Now I have to enter

$ sudo shutdown -h -P now

in a terminal to shutdown.

Is this a know problem and is there a solution? I haven't found anything in the forum.

#7 Re: Other Issues » Apt-get: DNS problem » 2018-12-01 09:01:30

giorgiob

@chris2be8: Thanks for the hints that led me to find the problem!
(Lesson learned: never tweak with a system and leave before you are finished with what you were trying to achieve.)

Indeed I had set

hosts files

in /etc/nsswitch.conf about two weeks ago. The reason, if I can remember correctly, was that my router was giving me wrong or outdated information for some hosts in my LAN.
So I had temporarily changed /etc/nsswitch.conf (without really understanding what I was doing). Then I had to leave and forgot to change the line back to

hosts files dns

I did it now and both apt-get and ntp work again.

Thanks to all of you for your time and useful information.

#8 Re: Other Issues » Apt-get: DNS problem » 2018-11-29 18:49:14

giorgiob
arnaiz wrote:

Try to use another mirror url:

deb http://pkgmaster.devuan.org/merged ascii main

and directly the main repository direction:

deb http://5.196.38.18/merged ascii main

and let see what happen.

The first option gives the same error:

$ sudo apt-get update
Err:1 http://pkgmaster.devuan.org/merged ascii InRelease
  Could not resolve 'pkgmaster.devuan.org'
Err:2 http://pkgmaster.devuan.org/merged ascii-security InRelease
  Could not resolve 'pkgmaster.devuan.org'
Err:3 http://pkgmaster.devuan.org/merged ascii-updates InRelease
  Could not resolve 'pkgmaster.devuan.org'
Err:4 http://pkgmaster.devuan.org/merged ascii-backports InRelease
  Could not resolve 'pkgmaster.devuan.org'
Reading package lists... Done
W: Failed to fetch http://pkgmaster.devuan.org/merged/dists/ascii/InRelease  Could not resolve 'pkgmaster.devuan.org'
W: Failed to fetch http://pkgmaster.devuan.org/merged/dists/ascii-security/InRelease  Could not resolve 'pkgmaster.devuan.org'
W: Failed to fetch http://pkgmaster.devuan.org/merged/dists/ascii-updates/InRelease  Could not resolve 'pkgmaster.devuan.org'
W: Failed to fetch http://pkgmaster.devuan.org/merged/dists/ascii-backports/InRelease  Could not resolve 'pkgmaster.devuan.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

I had tried the second option already: with that I can do

$ sudo apt-get update

but then if I upgrade, symbolic addresses are used at some points and these cannot be resolved.

#9 Re: Other Issues » Apt-get: DNS problem » 2018-11-29 18:39:00

giorgiob
chris2be8 wrote:

Try:
ping -c 1 deb.devuan.org

That should do the DNS lookup the same way as apt-get does.

Chris

As a normal user I get:

$ ping -c 1 deb.devuan.org
ping: socket: Operation not permitted

As root I get:

$ sudo ping -c 1 deb.devuan.org
ping: deb.devuan.org: Name or service not known

On the working laptop (from the same LAN), without root:

$ ping -c 1 deb.devuan.org
PING deb.roundr.devuan.org (37.187.111.86) 56(84) bytes of data.
64 bytes from ns327660.ip-37-187-111.eu (37.187.111.86): icmp_seq=1 ttl=54 time=56.4 ms

--- deb.roundr.devuan.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 56.463/56.463/56.463/0.000 ms

#10 Re: Other Issues » Apt-get: DNS problem » 2018-11-29 18:35:00

giorgiob

My /etc/hosts contains:

127.0.0.1	localhost laptop-1

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

where laptop-1 is also the host name contained in /etc/hostname

I do not see any difference wrt to the other laptop where everything works fine.

BTW, ntp does not work either: the time is off by one hour and ntp won't synchronize. I tried stopping the service and
forcing synchronization with

$ sudo service ntp stop

and then:

$  sudo ntpd -gq
29 Nov 18:28:06 ntpd[7737]: ntpd 4.2.8p10@1.3728-o Sun Feb 25 21:22:55 UTC 2018 (1): Starting
29 Nov 18:28:06 ntpd[7737]: Command line: ntpd -gq
29 Nov 18:28:06 ntpd[7737]: proto: precision = 1.606 usec (-19)
29 Nov 18:28:06 ntpd[7737]: Listen and drop on 0 v6wildcard [::]:123
29 Nov 18:28:06 ntpd[7737]: Listen and drop on 1 v4wildcard 0.0.0.0:123
29 Nov 18:28:06 ntpd[7737]: Listen normally on 2 lo 127.0.0.1:123
29 Nov 18:28:06 ntpd[7737]: Listen normally on 3 eth0 192.168.2.159:123
29 Nov 18:28:06 ntpd[7737]: Listen normally on 4 lo [::1]:123
29 Nov 18:28:06 ntpd[7737]: Listen normally on 5 eth0 [2003:73:f22:3f49:226:9eff:fe25:3db5]:123
29 Nov 18:28:06 ntpd[7737]: Listen normally on 6 eth0 [fe80::226:9eff:fe25:3db5%2]:123
29 Nov 18:28:06 ntpd[7737]: Listening on routing socket on fd #23 for interface updates

but it stops there indefinitely
On the working laptop it just takes a few seconds and I get:

$ sudo ntpd -gq
29 Nov 19:30:16 ntpd[11274]: ntpd 4.2.8p10@1.3728-o Sun Feb 25 21:22:55 UTC 2018 (1): Starting
29 Nov 19:30:16 ntpd[11274]: Command line: ntpd -gq
29 Nov 19:30:16 ntpd[11274]: proto: precision = 0.162 usec (-22)
29 Nov 19:30:16 ntpd[11274]: Listen and drop on 0 v6wildcard [::]:123
29 Nov 19:30:16 ntpd[11274]: Listen and drop on 1 v4wildcard 0.0.0.0:123
29 Nov 19:30:16 ntpd[11274]: Listen normally on 2 lo 127.0.0.1:123
29 Nov 19:30:16 ntpd[11274]: Listen normally on 3 eth0 192.168.2.108:123
29 Nov 19:30:16 ntpd[11274]: Listen normally on 4 lo [::1]:123
29 Nov 19:30:16 ntpd[11274]: Listen normally on 5 eth0 [2003:73:f22:3f49:3ad5:47ff:fed7:11cb]:123
29 Nov 19:30:16 ntpd[11274]: Listen normally on 6 eth0 [fe80::3ad5:47ff:fed7:11cb%2]:123
29 Nov 19:30:16 ntpd[11274]: Listening on routing socket on fd #23 for interface updates
29 Nov 19:30:17 ntpd[11274]: Soliciting pool server 178.238.225.189
29 Nov 19:30:18 ntpd[11274]: Soliciting pool server 138.201.64.208
29 Nov 19:30:18 ntpd[11274]: Soliciting pool server 213.202.247.29
29 Nov 19:30:19 ntpd[11274]: Soliciting pool server 129.250.35.250
29 Nov 19:30:19 ntpd[11274]: Soliciting pool server 37.58.57.238
29 Nov 19:30:19 ntpd[11274]: Soliciting pool server 2001:4ba0:ffa4:3d2:5:199:135:170
29 Nov 19:30:20 ntpd[11274]: Soliciting pool server 2a01:4f8:221:3c82::123
29 Nov 19:30:20 ntpd[11274]: Soliciting pool server 145.239.0.227
29 Nov 19:30:20 ntpd[11274]: Soliciting pool server 195.50.171.101
29 Nov 19:30:20 ntpd[11274]: Soliciting pool server 131.188.3.220
29 Nov 19:30:21 ntpd[11274]: Soliciting pool server 94.130.231.116
29 Nov 19:30:21 ntpd[11274]: Soliciting pool server 2a01:4f8:212:24c4::12
29 Nov 19:30:21 ntpd[11274]: Soliciting pool server 213.251.52.43
29 Nov 19:30:22 ntpd[11274]: Soliciting pool server 188.68.36.203
29 Nov 19:30:22 ntpd[11274]: Soliciting pool server 2a02:c207:2010:9464::1
29 Nov 19:30:23 ntpd[11274]: Soliciting pool server 94.130.76.108
29 Nov 19:30:23 ntpd[11274]: Soliciting pool server 85.214.38.116
29 Nov 19:30:25 ntpd[11274]: ntpd: time slew +0.001472 s
ntpd: time slew +0.001472s

So I am not making any progress at the moment.

#11 Other Issues » Apt-get: DNS problem » 2018-11-28 17:47:54

giorgiob
Replies: 10

I am not sure what the problem on my laptop is (running Devuan Ascii). Maybe I have interrupted
an upgrade a few days ago and some executables or configuration files got broken, no idea.

Anyway, apt-get has stopped working and is not able to resolve hostnames. For example:

$ sudo apt-get update
Err:1 http://deb.devuan.org/merged ascii InRelease
  Could not resolve 'deb.devuan.org'
Err:2 http://deb.devuan.org/merged ascii-security InRelease
  Could not resolve 'deb.devuan.org'
Err:3 http://deb.devuan.org/merged ascii-updates InRelease
  Could not resolve 'deb.devuan.org'
Err:4 http://deb.devuan.org/merged ascii-backports InRelease
  Could not resolve 'deb.devuan.org'
Reading package lists... Done
W: Failed to fetch http://deb.devuan.org/merged/dists/ascii/InRelease  Could not resolve 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/ascii-security/InRelease  Could not resolve 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/ascii-updates/InRelease  Could not resolve 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/ascii-backports/InRelease  Could not resolve 'deb.devuan.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

I have checked that /etc/resolv.conf contains the same nameserver that is configured on another laptop, on which apt-get works.
Also, dig works:

$ sudo dig  deb.devuan.org

; <<>> DiG 9.10.3-P4-Debian <<>> deb.devuan.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5203
;; flags: qr rd ra; QUERY: 1, ANSWER: 16, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;deb.devuan.org.			IN	A

;; ANSWER SECTION:
deb.devuan.org.		115	IN	CNAME	deb.roundr.devuan.org.
deb.roundr.devuan.org.	56996	IN	A	185.26.197.8
deb.roundr.devuan.org.	56996	IN	A	46.4.50.2
deb.roundr.devuan.org.	56996	IN	A	185.203.114.135
deb.roundr.devuan.org.	56996	IN	A	91.121.196.103
deb.roundr.devuan.org.	56996	IN	A	131.188.12.211
deb.roundr.devuan.org.	56996	IN	A	31.220.0.151
deb.roundr.devuan.org.	56996	IN	A	130.225.254.116
deb.roundr.devuan.org.	56996	IN	A	141.84.43.19
deb.roundr.devuan.org.	56996	IN	A	37.220.36.58
deb.roundr.devuan.org.	56996	IN	A	185.183.113.129
deb.roundr.devuan.org.	56996	IN	A	195.85.215.180
deb.roundr.devuan.org.	56996	IN	A	37.187.111.86
deb.roundr.devuan.org.	56996	IN	A	5.196.38.18
deb.roundr.devuan.org.	56996	IN	A	95.216.15.86
deb.roundr.devuan.org.	56996	IN	A	200.236.31.1

;; Query time: 1 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Wed Nov 28 17:38:17 CET 2018
;; MSG SIZE  rcvd: 307

and nslookup gives:

$ nslookup de.deb.devuan.org
Server:		192.168.2.1
Address:	192.168.2.1#53

Non-authoritative answer:
de.deb.devuan.org	canonical name = pkgmaster.devuan.org.
Name:	pkgmaster.devuan.org
Address: 5.196.38.18

192.168.2.1 is the nameserver configured in the resolv.conf file.

I have no idea what I should check next: why are dig and nslookup resolving correctly while apt-get is not?

#12 Re: Installation » Installing devuan to lvm partitions within dm-crypt container » 2018-02-21 13:18:01

giorgiob

My encrypted partitions are working but I have a problem when shutting down the system: The console blocks and displays the message

Stopping remaining crypt disks...sda2_crypt(busy)

several times. After about one minute it displays an error message

stopping early crypto disks failed.

and the system is shut down.

It seems this is not a really issue and it has been known for ages (https://bugs.debian.org/cgi-bin/bugrepo … bug=575652) but
it is a bit annoying to see this happening each time I switch my computer off.
Also, I use this setup for most friends who want to install Linux on their laptops, so I see it pretty often.

Do you know if there is any plan to address this issue?

#13 Re: Installation » Cannot switch to text console on a freshly installed Devuan system » 2018-01-25 21:58:50

giorgiob

I have upgraded to Devuan Ascii and now the problem is gone.

#14 Re: Installation » Cannot switch to text console on a freshly installed Devuan system » 2018-01-23 21:13:36

giorgiob
fsmithred wrote:

Make sure you have consolekit, libpam-ck-connector and policykit-1 installed. Any of those missing has been a source of authentication problems for others. Maybe look at some of the discussions about mate on this forum. I don't know if anyone else has had this problem. (Usual problems are with shutdown/reboot and mounting removable media.)

I checked and all three packages are installed.

#15 Re: Installation » Cannot switch to text console on a freshly installed Devuan system » 2018-01-22 18:30:03

giorgiob
fsmithred wrote:

Not a problem here. I can get to tty1-6 from the login screen or from the desktop. Say a little more about how and what you installed. Full desktop? Minimal install and then added stuff?

Is there some other key you need to press to get the function keys to work on this laptop?

In the text installer I have chosen Mate Desktop. It came with slim. Afterwards I have installed wdm and lightdm.

All three display managers have the same problem: CTRL-ALT-F1 does not open tty1, instead it restarts the display manager
and goes to the greeter. My laptop has a Fn key between CTRL and ALT. I have tried CTRL-Fn-ALT-F1, CTRL-Fn-F1, Fn-ALT-F1, Fn-F1,
but nothing happens. Only CTRL-ALT-F1 has an effect: it switches to the login screen as already described.

I have another older laptop and a desktop with Devuan Jessie but on them everything works fine.

I have opened a shell on the laptop using ssh. Below is the output of  tail -f /var/log/lightdm/lightdm.log when I press CTRL-ALT-F1.
As you can see, the X server is terminated immediately. Also, there is a ConsoleKit warning that I do not understand.
Maybe some shortcuts are messed up? As far as I can remember, killing the X server should be CTRL-ALT-Backspace.

[+1158.27s] DEBUG: Process 3636 terminated with signal 11
[+1158.27s] DEBUG: DisplayServer x-0: X server stopped
[+1158.27s] DEBUG: Releasing VT 7
[+1158.27s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+1158.27s] DEBUG: Seat: Display server stopped
[+1158.27s] DEBUG: Seat: Stopping session
[+1158.27s] DEBUG: Session pid=3654: Sending SIGTERM
[+1158.27s] DEBUG: Seat: Stopping session
[+1158.27s] DEBUG: Session pid=3683: Sending SIGTERM
[+1158.27s] DEBUG: Seat: Active display server stopped, starting greeter
[+1158.27s] DEBUG: Seat: Creating greeter session
[+1158.27s] DEBUG: Seat: Creating display server of type x
[+1158.27s] DEBUG: Using VT 7
[+1158.27s] DEBUG: Seat: Starting local X display on VT 7
[+1158.27s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+1158.27s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+1158.27s] DEBUG: DisplayServer x-0: Launching X Server
[+1158.27s] DEBUG: Launching process 3692: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+1158.28s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+1158.28s] DEBUG: Session pid=3683: Terminated with signal 15
[+1158.28s] DEBUG: Session: Failed during authentication
[+1158.28s] DEBUG: Seat: Session stopped
[+1158.34s] DEBUG: Session pid=3654: Greeter closed communication channel
[+1158.34s] DEBUG: Session pid=3654: Exited with return value 0
[+1158.34s] DEBUG: Seat: Session stopped
[+1158.34s] DEBUG: Seat: Stopping display server, no sessions require it
[+1158.97s] DEBUG: Got signal 10 from process 3692
[+1158.97s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+1158.97s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+1158.98s] DEBUG: Seat: Display server ready, starting session authentication
[+1158.98s] DEBUG: Session pid=3711: Started with service 'lightdm-greeter', username 'lightdm'
[+1159.03s] DEBUG: Session pid=3711: Authentication complete with return value 0: Success
[+1159.03s] DEBUG: Seat: Session authenticated, running command
[+1159.03s] DEBUG: Session pid=3711: Running command /usr/sbin/lightdm-gtk-greeter
[+1159.03s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+1159.03s] DEBUG: Session pid=3711: Logging to /var/log/lightdm/x-0-greeter.log
[+1159.08s] DEBUG: Activating VT 7
[+1159.08s] DEBUG: Activating ConsoleKit session 98255d81a70a6f4819439a685a633043-1516645474.422095-851764063
[+1159.08s] WARNING: Error activating ConsoleKit session: GDBus.Error:org.freedesktop.DBus.GLib.UnmappedError.CkVtMonitorError.Code0: Session is already active
[+1159.31s] DEBUG: Session pid=3711: Greeter connected version=1.10.3
[+1159.66s] DEBUG: Session pid=3711: Greeter start authentication
[+1159.66s] DEBUG: Session pid=3739: Started with service 'lightdm', username '(null)'
[+1159.67s] DEBUG: Session pid=3739: Got 1 message(s) from PAM
[+1159.67s] DEBUG: Session pid=3711: Prompt greeter with 1 message(s)

#16 Re: Installation » Cannot switch to text console on a freshly installed Devuan system » 2018-01-21 12:03:00

giorgiob
spartrekus.git wrote:
giorgiob wrote:

Yesterday I performed a fresh install of Devuan Jessie on my ASUS laptop. Everything seemed to go fine but then I noticed that I cannot switch to a console with CTRL-ALT-F{1, 2, 3, 4, 5, 6} from the Slim login. If I try this after I have logged in, the user gets logged and I am brought back to the Slim login.

Is this a known problem or can it be that I have to configure something on my system?

this is very strange. it could be a bug.

could you try : apt-get install wdm

install wdm by default. reboot, and try ctrl f1,....

let us know about this test.

(I note: you know there is a huge bug with /dev/video !! permissions are wrong under devuan for some x11 things. one day someone will find out.)

Thanks for the hint. I tried both wdm and lightdm but they behave in the same way as slim: CTRL-ALT-F1 brings me back to the greeter. This happens even if I am logged in as root. Do I need to change the permissions of /dev/video in some way?

#17 Installation » Cannot switch to text console on a freshly installed Devuan system » 2018-01-21 09:08:27

giorgiob
Replies: 8

Yesterday I performed a fresh install of Devuan Jessie on my ASUS laptop. Everything seemed to go fine but then I noticed that I cannot switch to a console with CTRL-ALT-F{1, 2, 3, 4, 5, 6} from the Slim login. If I try this after I have logged in, the user gets logged and I am brought back to the Slim login.

Is this a known problem or can it be that I have to configure something on my system?

#18 Re: Installation » Installing devuan to lvm partitions within dm-crypt container » 2018-01-21 08:58:10

giorgiob

I have performed an install with an encrypted disk yesterday using the text-based installer of the devuan jessie image (devuan_jessie_1.0.0_amd64_NETINST.iso) and I can confirm what Simplicio sketched.

In the partition manager I chose manual partitioning and then first set up the unencrypted partitions (/dev/sda1 for /boot, /dev/sda2 for all the rest). Then I used dm-crypt to encrypt /dev/sda2, which created a new device /dev/mapper/sda2_crypt.
Then I had to define an LVM group inside /dev/mapper/sda2_crypt and add logical volumes (partitions) to it. They got mapped to /dev/mapper/vg-rootfs and /dev/mapper/vg-swap. Finally I used the last two mapped devices to install Devuan.

Pages: 1

Board footer

Forum Software