On Mon, 14 Aug 2023 at 12:47, Andrey Dogadkin wrote:
> Should you specifically need UEFI next time, an alternative solution
> can be to temporarily disable KVM paravirtualization (default for
> Linux-based guests). It can be reenabled back after you are done with
> installation. See
> https://bug
On Sat, 12 Aug 2023 at 17:40, wrote:
> I see there that he has two possible solutions:
>
> - Install 11, then upgrade to 12, which option you don't care for.
>
> - Install in legacy-boot mode, rather than in UEFI mode.
>
> Is the second option viable for you?
That was it, EFI! Normally when I
On Sat, 12 Aug 2023 at 13:35, wrote:
> I notice on the video you provided a reference to not finding a virtual
> core keyboard, in addition to the xf86SetGamma message. Maybe there's
> something in the keyboard and/or USB settings for the VM?
There are USB settings in the VB VM configuration, how
On Sat, 12 Aug 2023 at 13:16, wrote:
> How about selecting the non-graphical install (one downarrow-press
> away, I believe)?
I had tried that too. In that case the screen becomes gray and nothing
visible happens. Clearly something changed in Debian itself, because
in these tests I use the same
Installation of Debian 11.7 on VirtualBox works fine. This video shows
the beginning of the process, I press Return on the default first
option, Graphics Install:
https://drive.google.com/file/d/1tSRFAPvcO6YTkxPPinO0EQjnBMJWAegg/view?usp=sharing
Installation of Debian 12.1 on VirtualBox fails at t
On Sun, 31 Jul 2022 at 13:49, David wrote:
> > It seems like preseeding requires the building of an iso? If so that
> > is not I was looking for as there is a bit of work to do that that!
>
> You haven't explained what you're thinking, or why, but it sounds wrong.
> Most people would preseed a pr
On Sat, 30 Jul 2022 at 03:04, David Wright wrote:
> People with more experience of preseeding might comment on
> whether this suggestion would work. I notice that this option
> is available, which might be what you want:
It seems like preseeding requires the building of an iso? If so that
is not
When using netinst iso to install Debian, one is offered the
possibility of guided install with encrypted LVM. if such a choice is
made the installer fills the partition with random data. That is
generally the correct thing to do but in some cases that is not needed
or desired and it is an inconven
On Sat, 16 Jul 2022 at 23:41, Brian wrote:
> But you did not download and try the one I suggested? Therefore, you
> are working blindfolded. It is dated 2022-0 7-05. The archive modules
> may match the d-i kernel.
I successfully installed Sid using the Bullseye mini.iso that I
downloaded from th
On Sat, 16 Jul 2022 at 21:02, Piscium wrote:
> I chose "Execute Shell", got a window with instructions that mentions
> /target, was dropped into BusyBox, and strangely enough there is no
> /target in the RAM disk. The other usual folders at the root are there
> (/bin,
On Sat, 16 Jul 2022 at 19:26, Charles Curley
wrote:
> Look in the installation logs for suspicious messages. During
> installation, they are at /target/var/log/installer/. After you reboot
> into the newly installed system, they are at /var/log/installer/.
I chose "Execute Shell", got a window w
On Sat, 16 Jul 2022 at 19:49, Brian wrote:
>
> On Sat 16 Jul 2022 at 18:27:29 +0100, Piscium wrote:
> > [1] https://wiki.debian.org/DebianUnstable
> > [2] deb.debian.org
>
> Is the mini.iso at
>
>
> http://ftp.nl.debian.org/debian/dists/bullseye/main/insta
Hiya,
I tried to install Sid (on a VirtualBox VM) following the instructions
in [1], section "Use the Unstable "mini.iso" image.". I downloaded the
specified ISO, did the sha256 check, proceeded with all the various
options without any error, network configuration also succeeded, then
at the step
On Wed, 6 Jul 2022 at 03:19, Piscium wrote:
> I won't bother changing the name, I was just curious.
In the end I changed the name of the LUKS partition. It was easy. I am
posting here the commands in case someone else is interested.
As root:
1. dmsetup rename /dev/mapper/oldname n
On Wed, 6 Jul 2022 at 03:35, David Wright wrote:
> A dozen or so lines from the end of /var/log/installer/syslog,
> you'll probably see a line like:
>
> Apr 17 01:43:04 cdrom-detect: Unmounting and ejecting '/dev/sdXn'
>
> which is the d-i "ejecting" the "CD" that the installer was on.
Thanks, D
On Wed, 6 Jul 2022 at 03:06, David wrote:
>
> Because the drive with the LUKS partition was identified as sdb
> when the installer was running. Perhaps the installer was running
> from sda. This name 'sdb3_crypt' is just an arbitrary string used
> to name the LUKS volume in /etc/crypttab. You can'
Hi,
Recently I installed bullseye on a PC using netinst. During
installation I used the automatic installer and chose encrypted mode
with some space left empty. This is what I got:
root@backup-server:~# lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda
17 matches
Mail list logo
