You are not logged in.
Pages: 1
Adding to xorg.conf is a red herring, imo – there's no issue with the keyboard layout in X, or after X has started, e.g., unlocking the screensaver.
After logging in and press key combination of Ctrl+ Alt+ F1 I don't get a console but back to login screen after a brief black screen with my login details.
That is not normal. What about with the other virtual consoles (Ctrl-Alt-F2 to -F6)? It this a standard desktop keyboard or a laptop with other functions on the Fn keys? Do you have proprietary (i.e., nVidia) graphics?
... there was reference to a
... dirty bit ...
Dirty filesystem, usually caused by abruptly switching off instead of shutting down gracefully. Should be fixable by fsck, but the partition must be unmounted to do that.
Edit: typo.
globalgoldfish wrote:Now run setupcon to have the your default keyboard settings applied to the console.
The console-setup package is supposed to ...
Agreed. The console is also supposed to follow /etc/default/keyboard at boot, but it doesn't. At least, it doesn't here. I just suggested the steps that I took to get my keyboard preference everywhere – X session, user and root tty, and login screen.
The standard installer generally sets all this, only asking once. The Devuan desktop live doesn't, which is where I came across a similar situation to the OP.
... if I leave the machine for some time and it logs me out, I can enter my password with the hash key - but not at login!
Before you log in, your user preferences are not known. Try this:
After logging in, change to a console (e.g., Ctrl-Alt-F1) and log in as root – you'll probably have to use Shift-3 for the # symbol. Having logged in, run dpkg-reconfigure keyboard-configuration again. This shouldn't be necessary, but ... just to be sure.
Now run setupcon to have the your default keyboard settings applied to the console. After that, you should get a # on the console when you press that key; Shift-3 should give you £. Now try rebooting and see what you get at the login screen.
Incidentally, I agree with what's been said – pc105 and gb for a standard UK keyboard.
Just a PS to say that silently removing the netboot files completely is a bit disappointing. That makes Devuan the only (afaik) Linux distribution that can't be installed by PXE boot.
Thanks for your response. I don't actually want the mini.iso image (nor beowulf – see title).
The netboot linux and initrd.gz are the important files. They are essential for booting into the installer by PXE (iPXE) – this is not the same as netinstall – and (afaik) there are no alternative files that allow this.
This is part of my current iPXE menu, showing the Debian and Devuan install entries for comparison:
:debian
kernel http://debian.proxad.net/debian/dists/stable/main/installer-${archl}/current/images/netboot/debian-installer/${archl}/linux initrd=initrd.gz vga=791 quiet
initrd http://debian.proxad.net/debian/dists/stable/main/installer-${archl}/current/images/netboot/debian-installer/${archl}/initrd.gz
boot || goto failed
goto start
:devuan
set base-url ${httpboot-url}boot/devuan/installer/ascii/${archl}/
kernel ${base-url}linux initrd=initrd.gz vga=791 quiet
initrd ${base-url}initrd.gz
boot || goto failed
goto start
The Devuan files are from the same path in the Devuan tree as the Debian files, but stored locally rather than being called from the mirror at boot. Any suggestions for alternative file targets to make the Devuan installer work are welcome.
Hello,
The netboot files and the mini.iso image (e.g., ascii/main/installer-amd64/current/images/netboot and other archs) haven't been updated in line with the rest of Devuan. This means that they are currently unusable because of a mismatch between kernel version (in mini.iso) and kernel modules (in the repo.).
Is this intended, or just an oversight, or work-in-progress, please? The linux and initrd.gz files there are required for PXE booting.
Pages: 1