You are not logged in.
Pages: 1
Hi all,
With all your explanations I am able to boot with the minimal image and to
install the system in a very similar way as with the graphical install.
My last problem is that the grub entry is incorrectly generated.
Grub is starting now in text mode after I have corrected the file "/etc/default/grub" to allow serial
console for grub. Unfortunately I am not able to start the Linux
kernel in text mode.
Setting GRUB_CMDLINE_LINUX="console=ttyS0,115200n8" is not enough to switch
the loading of the kernel in text mode.
I will do further research and keep you informed of the results. Anyway, if you
have some new ideas, I will be very happy. It's a little painful to start again and again
the system on the USB stick to correct the installed system.
best regards
I have tried the instruction
init=/bin/sh
but the system does not boot.
Anyway, I think this is not very useful, since the file system on the USB stick is in format
squashfs (a read-only compressed file system). It is impossible to modify it without rebuilding it.
I think the only one solution is "netinst" image. It would be interesting however
if the "minimal-live" image had the possibility to boot over serial line.
In order to have only one encrypted partition, one has to work with the "netinst" image
and do the job manually. It is doubtful if this is really interesting since typing
the passphrase at each boot is certainly not usable. Perhaps by using
a special GPG key to unlock the partition, full disk encryption is practical.
The interest to have a such solution is that, if the disk is broken, it can be replaced
without worrying about to erase it (which is often impossible if the disk is broken).
Contrary to what is suggested in a previous post, the Debian installation manual
is not very helpful. It states explicitely that it is impossible to have
"/boot" and the rest of the system on a single encrypted partition.
I have made some progress by trying the image "minimal-live". Without too much success.
After editing the grub entry to add "console=ttyS0,115200n8" the system start booting but
after the start of the openssh server just hangs.
Before hanging, 3 strange sounds are emited by the APU (which has no speaker!).
I have tried the grub entry "std" and "access to ram" with the same effect and
the entry which disable the different probes. With these latter the system hangs but elsewhere in the boot process.
Hello,
Thanks for the tip. I have googled but with "Devuan" instead of "Debian". Soon
after my post, I have found this page https://teklager.se/en/knowledge-base/i … apu-board/
which was helpful. I have forgotten how Devuan is near (at least on some features)
of the Debian distribution.
Unfortunately, by using the netinst image it is not possible to have the
directory "/boot" and the rest of the system on the same encrypted partition.
At least not automatically.
I would appreciate some pointers on how to do that manually (the installer provided
with the "desktop-live" image permit to have only one encrypted partition
but without giving indications on how this is achieved).
Is it possible to have only one encrypted partition with the image "minimal-live"?
I haven't yet tried it and I don't know if it is possible to add the required instructions
to the grub entry and if it allows only one encrypted partition.
Thanks for your help,
Best regards,
Nemo76
Hi All,
I plan to install Devuan on an APU machine from PC Engines
(https://www.pcengines.ch). This is a quite classical PC except
that it has no graphic card and no keyboard. It works only with a serial console.
A lot of linux run on it, but I have no idea how I can install
devuan by using a serial console. I have looked on most CD (live ISO, netinst and minimal)
without finding a grub menu entry for booting with a serial console.
I suppose I should pass the commands manually at the grub prompt.
If anyone could give me some hints, this will be very helpful for me.
Thanks,
nemo76
Hi,
Thanks for the tip. the packages "grub-efi-amd64" and "grub-efi-amd64-signed" were installed. After the
following manipulations, the system boots again:
1) apt remove --purge grub-efi-amd64-signed
2) rm -rf /boot/efi/EFI/devuan
3) grub-install /dev/sda
By the way, I have used the ISO Super Grub Disk (https://www.supergrubdisk.org) to boot more easily
my system. With this ISO, it was possible to unlock the encrypted disk and then
to find the file "grub.cfg" inside the crypted file system without having
to type the very long UUID (which should be first copied on a sheet of paper
with a pen).
Thanks for your help.
Best regards.
Hi All,
I have installed Devuan ASCII version in a unique encrypted partition (containing "/boot")
on an UEFI system.
On ASCII, to boot the system the utility "grubx64.efi" is used after a modification which
insert in the executable the grub command "cryptodisk uuid" with the UUID of the
crypted disk.
In Beowulf, however the file "grub.cfg" is used. The file contains the commands to start
the system with "grubx64.efi". The commands inside the file
"grub.cfg" are correct (I have painfully passed them in the grub shell and
the system has started), but since the file "grub.cfg" is not found the system
can not be started easily.
I have first noticed this problem on a real machine but I was able
to reproduce it in VirtualBox (with UEFI Bios).
Do you have an idea of a solution?
Best regards,
Pages: 1