Bug#923091: marked as done (base-installer: Allow installing w/o the broken merged-usr-via-symlinks)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 12:31:36 +0100
with message-id <20240319113136.w3x36ynyk4jjv...@shell.thinkmo.de>
and subject line Re: Bug#923091: base-installer: Allow installing w/o the 
broken merged-usr-via-symlinks
has caused the Debian Bug report #923091,
regarding base-installer: Allow installing w/o the broken 
merged-usr-via-symlinks
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
923091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base-installer
Version: 1.187
Severity: wishlist

Hi!

The current base-installer uses the default debootstrap settings
which end up unconditionally installing systems with the
merged-usr-via-symlinks deployment method which is broken by design,
please see:

  <https://lists.debian.org/debian-devel/2019/02/msg00251.html>

I'm aware the original request to change the debootstrap default got
unfortunately moved to the tech-ctte. :(

But regardless of that outcome I'd like to request to have a way to
install using debootstrap's --no-merged-usr option, to not have to
install from stretch and then upgrade to buster, or having to drop into
a shell and do manual stuff from within the installer.

In addition it would be also nice if that option was passed whenever
/usr is not on its own partition, because then the properties from
the merged-/usr concept are not relevant anymore, but we get all the
downsides of the broken deployment method.

If this was to be applied for buster, I'd be happy to provide patches.

Otherwise I guess I might need to end up looking to generate
alternative netinst somewhere else or something. :(

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
On Sun, Feb 24, 2019 at 03:10:17AM +0100, Guillem Jover wrote:
> I'm aware the original request to change the debootstrap default got
> unfortunately moved to the tech-ctte. :(

And ctte made an decision.  So there is no bug here.  Closing.

Bastian

-- 
Violence in reality is quite different from theory.
-- Spock, "The Cloud Minders", stardate 5818.4--- End Message ---

Bug#1058638: grub-installer: boot fails: $bootdev empty [BIOS/MBR, Vista, 2 disks]: Installing grub on ''

[Tj]

Source: grub-installer
Version: 1.194
Followup-For: Bug #1058638

I fetched the proposed patch and applied it to grub-installer inside the
installer and can confirm it solved this issue.

syslog now shows "grub-installer: info: Installing grub on '/dev/vdb'
and examining sector 0 of the disk image file shows the expected
boot-strap code and a reboot correctly starts Debian:

hexdump -n 512 -C disk2-debian-12.bin
  eb 63 90 10 8e d0 bc 00  b0 b8 00 00 8e d8 8e c0  |.c..|
0010  fb be 00 7c bf 00 06 b9  00 02 f3 a4 ea 21 06 00  |...|.!..|
0020  00 be be 07 38 04 75 0b  83 c6 10 81 fe fe 07 75  |8.uu|
0030  f3 eb 16 b4 02 b0 01 bb  00 7c b2 80 8a 74 01 8b  |.|...t..|
0040  4c 02 cd 13 ea 00 7c 00  00 eb fe 00 00 00 00 00  |L.|.|
0050  00 00 00 00 00 00 00 00  00 00 00 80 01 00 00 00  ||
0060  00 00 00 00 ff fa 90 90  f6 c2 80 74 05 f6 c2 70  |...t...p|
0070  74 02 b2 80 ea 79 7c 00  00 31 c0 8e d8 8e d0 bc  |ty|..1..|
0080  00 20 fb a0 64 7c 3c ff  74 02 88 c2 52 be 80 7d  |. ..d|<.t...R..}|
0090  e8 17 01 be 05 7c b4 41  bb aa 55 cd 13 5a 52 72  |.|.A..U..ZRr|
00a0  3d 81 fb 55 aa 75 37 83  e1 01 74 32 31 c0 89 44  |=..U.u7...t21..D|
00b0  04 40 88 44 ff 89 44 02  c7 04 10 00 66 8b 1e 5c  |.@.D..D.f..\|
00c0  7c 66 89 5c 08 66 8b 1e  60 7c 66 89 5c 0c c7 44  ||f.\.f..`|f.\..D|
00d0  06 00 70 b4 42 cd 13 72  05 bb 00 70 eb 76 b4 08  |..p.B..r...p.v..|
00e0  cd 13 73 0d 5a 84 d2 0f  83 d8 00 be 8b 7d e9 82  |..s.Z}..|
00f0  00 66 0f b6 c6 88 64 ff  40 66 89 44 04 0f b6 d1  |.fd.@f.D|
0100  c1 e2 02 88 e8 88 f4 40  89 44 08 0f b6 c2 c0 e8  |...@.D..|
0110  02 66 89 04 66 a1 60 7c  66 09 c0 75 4e 66 a1 5c  |.f..f.`|f..uNf.\|
0120  7c 66 31 d2 66 f7 34 88  d1 31 d2 66 f7 74 04 3b  ||f1.f.4..1.f.t.;|
0130  44 08 7d 37 fe c1 88 c5  30 c0 c1 e8 02 08 c1 88  |D.}70...|
0140  d0 5a 88 c6 bb 00 70 8e  c3 31 db b8 01 02 cd 13  |.Zp..1..|
0150  72 1e 8c c3 60 1e b9 00  01 8e db 31 f6 bf 00 80  |r...`..1|
0160  8e c6 fc f3 a5 1f 61 ff  26 5a 7c be 86 7d eb 03  |..a.&Z|..}..|
0170  be 95 7d e8 34 00 be 9a  7d e8 2e 00 cd 18 eb fe  |..}.4...}...|
0180  47 52 55 42 20 00 47 65  6f 6d 00 48 61 72 64 20  |GRUB .Geom.Hard |
0190  44 69 73 6b 00 52 65 61  64 00 20 45 72 72 6f 72  |Disk.Read. Error|
01a0  0d 0a 00 bb 01 00 b4 0e  cd 10 ac 3c 00 75 f4 c3  |...<.u..|
01b0  00 00 00 00 00 00 00 00  13 43 3c 32 00 00 80 04  |.C<2|
01c0  01 04 83 fe c2 ff 00 08  00 00 00 90 3b 00 00 00  |;...|
01d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
01f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..U.|
0200

Bug#1058638: grub-installer: boot fails: $bootdev empty [BIOS/MBR, Vista, 2 disks]: Installing grub on ''

[Tj]

Source: grub-installer
Version: 1.194
Followup-For: Bug #1058638

I think this may be due to the same cause as #1035096 and possibly also
#1035085

Bug#1058638: grub-installer: boot fails: $bootdev empty [BIOS/MBR, Vista, 2 disks]: Installing grub on ''

[Pascal-liste]

Hello,

On 13/12/2023 at 20:45, Tj wrote:


After a lot of code-chasing it appears the problem is that
grub-installer script fails to set its $bootdev variable:

grub-installer: info: Installing grub on ''

(note the empty quotes)

The target system has two 'disks'. The first has Microsoft Windows Vista
with 2 NTFS partitions using msdos label/MBR. The second is empty and intended
for the Debian OS and boot-loader.

The system boots in BIOS/Legacy/CSM mode.


I suspect this is yet another avatar of bug #1035096, for which I 
submitted a patch, see 
<https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/17>.

Bug#1058638: grub-installer: boot fails: $bootdev empty [BIOS/MBR, Vista, 2 disks]: Installing grub on ''

[Tj]

Source: grub-installer
Version: 1.194
Severity: important
Tags: d-i

Whilst helping user "mavaviij" in matrix Debian room I was able to
reproduce in a virtual machine a bug that causes the Debian install to
fail to boot with a blinking cursor after install.

After a lot of code-chasing it appears the problem is that
grub-installer script fails to set its $bootdev variable:

grub-installer: info: Installing grub on ''

(note the empty quotes)

The target system has two 'disks'. The first has Microsoft Windows Vista
with 2 NTFS partitions using msdos label/MBR. The second is empty and intended
for the Debian OS and boot-loader.

The system boots in BIOS/Legacy/CSM mode.

I've not been able to trace back through the code to figure out why the
failure occurs. I have however identifed what may be a clue: the Debian
OS disk sector 0 appears to contain GRUB's g2hdr.img which makes me
wonder if grub-ntldr-img was used - although not sure how that is done
and see no sign of it in the (saved) installer logs.

Reproducer:

Using debian-12.4.0-amd64-netinst.iso

fallocate -l 10 disk1-windows-vista.bin
fallocate -l 20 disk2-debian-12.bin
fdisk disk1-windows-vista.bin
#new: 1, default,512M
#type: 1, 07
#new: 2, default, default
#type: 2, 07
#write

sudo losetup -P --show -f disk1-windows-vista.bin
# /dev/loop0
sudo mount /dev/loop0p1 /mnt/tmp/
# fool os-prober into detecting Vista
sudo mkdir /mnt/tmp/boot
sudo touch /mnt/tmp/bootmgr
echo "W i n d o w s   V i s t a " | sudo dd of=/mnt/tmp/boot/bcd

find /mnt/tmp/ -ls; hexdump -C /mnt/tmp/boot/bcd
5  4 drwxrwxrwx   1 root root 4096 Dec 13 14:41 
/mnt/tmp/
   64  0 drwxrwxrwx   1 root root0 Dec 13 14:42 
/mnt/tmp/boot
   65  1 -rwxrwxrwx   1 root root   27 Dec 13 14:32 
/mnt/tmp/boot/bcd
   67  0 -rwxrwxrwx   1 root root0 Dec 13 14:41 
/mnt/tmp/bootmgr
  57 20 69 20 6e 20 64 20  6f 20 77 20 73 20 20 20  |W i n d o w s   |
0010  56 20 69 20 73 20 74 20  61 20 0a |V i s t a .|
001b

sudo umount /mnt/tmp
sudo os-prober
/dev/loop0p1:Windows Vista:Windows:chain

Now create a (libvirt/QEMU) VM guest with the 2 disk images attached and
go through the install procedure choosing the unpartitioned second disk
as the target.
At the question about installing the boot loader to the "primary disk"
answer No, then when the option to select which boot device to use choose
the 2nd disk where Debian is installed.

Save debug logs, restart VM, and even if using the SeaBIOS boot menu via
pressing Esc key, choosing the VirtIO boot device results in blinking
cursor.

Examine disk images and note that disk2 appears to have GRUB's g2hdr.img
in sector 0.

hexdump -C -n 512 disk2-debian-12.bin
  fa b8 00 10 8e d0 bc 00  b0 b8 00 00 8e d8 8e c0  ||
0010  fb be 00 7c bf 00 06 b9  00 02 f3 a4 ea 21 06 00  |...|.!..|
0020  00 be be 07 38 04 75 0b  83 c6 10 81 fe fe 07 75  |8.uu|
0030  f3 eb 16 b4 02 b0 01 bb  00 7c b2 80 8a 74 01 8b  |.|...t..|
0040  4c 02 cd 13 ea 00 7c 00  00 eb fe 00 00 00 00 00  |L.|.|
0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
01b0  00 00 00 00 00 00 00 00  13 43 3c 32 00 00 00 04  |.C<2|
01c0  01 04 83 fe c2 ff 00 08  00 00 00 90 3b 00 00 00  |;...|
01d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
01f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..U.|
0200


NOTE: on an UEFI system doing the reproducer one needs to edit 

/usr/lib/os-probes/mounted/20microsoft

and comment out the test for UEFI on lines 11-14 if wanting to manually
test os-prober outside the running installer.

Re: Installing, booting, logical problem shown by D-I

[yxcv]

Sun, 19 Nov 2023 20:55:16 +0100
 Pascal Hambourg  wrote:


Hi Matthias !



And! What does  B  K  ESP mean?


"B" means "boot" because partman stupidly confuses the ESP type and 
the boot flag on GPT.

"K" means "keep", do not reformat the partition.

Oh!
Thank you.

Re: Installing, booting, logical problem shown by D-I

[Pascal Hambourg]

Hi Matthias !
Your mail appears to be a bit confused.

On 19/11/2023 at 12:03, y...@vienna.at wrote:

I have a working machine with bookworm. Really nice one.
It happen to be booted from an  USB stick with DB12 SCSI10 for the moment


What does "DB12 SCSI10" mean ?

And I want it to bring Debian 12 from this stick SCSI10 to another 
stick, SCSI9!


What do you mean by "bring" ? Install ?

which is prepared with db12-live now, but should be useable as quite 
normal bookworm on other machines.


What do you mean by "prepared with db12-live" ? Did you write some live 
system image on it ?



working machine  with /dev/nvme0n1, part of RAID!
       1   MB     Freier Speicher
Nr.:1   536,9 MB  B  K  ESP
Nr.:2   998,6 GB   ext4
Nr.:3   1   GB       F  SWAP
            728  KB Freier Speicher

SCSI9   (0.0.0)(sda)  126,6 GB  Disk 3,0 to be installed,  with DB12 
"live".iso now.

   To be replaced by regular DB12.
SCSI10 (0.0.0)(sdd)      7,9 GB  Source disk with DB12.iso as the source 
and with D-I


What is DB12.iso ?


Problem: The working machine cannot be changed, therefore SCSI10 is booted.


What do you mean ?


And SCSI9 has to be partioned.
But! Partioning tries to influence the working machine,  especially N 
r.:1, of course NR..3 too!


What do you mean by "influence" ?


And! What does  B  K  ESP mean?


"B" means "boot" because partman stupidly confuses the ESP type and the 
boot flag on GPT.

"K" means "keep", do not reformat the partition.

Installing, booting, logical problem shown by D-I

[yxcv]

I have a working machine with bookworm. Really nice one.
It happen to be booted from an  USB stick with DB12 SCSI10 for the moment

And I want it to bring Debian 12 from this stick SCSI10 to another stick, 
SCSI9!
which is prepared with db12-live now, but should be useable as quite normal 
bookworm on other machines.

Here is the table shown by debian-install and its partitionering
  


working machine  with /dev/nvmw0n1, part of RAID!
      1   MB     Freier Speicher
Nr.:1   536,9 MB  B  K  ESP
Nr.:2   998,6 GB   ext4
Nr.:3   1   GB       F  SWAP
           728  KB Freier Speicher

SCSI9   (0.0.0)(sda)  126,6 GB  Disk 3,0 to be installed,  with DB12 
"live".iso now. 

  To be replaced by regular DB12.
SCSI10 (0.0.0)(sdd)      7,9 GB  Source disk with DB12.iso as the source and 
with D-I


Problem: The working machine cannot be changed, therefore SCSI10 is booted.
   And SCSI9 has to be partioned. 
But! Partioning tries to influence the working machine,  especially N r.:1, 
of course NR..3 too!

And! What does  B  K  ESP mean?

Thanks for reading up to here:-)
Ciao
Matthias

Re: Add Feature Prevent Installing non-free-firmware in Noraml Mode (Like expert mode)

[Holger Wansing]

Hi,

Am 1. November 2023 10:27:16 MEZ schrieb Modaresi Soft Hard 
:
>Hello. From Debian 12 onwards, proprietary drivers will be automatically 
>installed in normal mode.
>
>Can you make the installer ask questions in normal mode for installing 
>proprietary drivers?
>(Like a check box with No and Yes)

Based on the assumption, that for the vast majority of users it's wanted
to have non-free firmware installed, this is the default behavior.
If this is not wanted, you can use the parameter "firmware=never".

>What does firmware=never do? # 
>https://wiki.debian.org/Firmware#How_to_disable_detection_and_use_of_non-free_firmware
>
>Does firmware=never affect the installation and detection of free firmwares?

Detection of firmware still works, but you don't get non-free firmware 
installed automatically
(from the install media or via web).
In such situation, the installer may ask for firmware files nevertheless, 
if a device is detected, which requires this. 
You can provide such file then via USB stick for example, if you want.
This is the same behaviour as in Debian 11 and before.

Free firmware is not affected at all by this.


Holger




-- 
Sent from /e/ OS on Fairphone3

Re: Add Feature Prevent Installing non-free-firmware in Noraml Mode (Like expert mode)

[Lennart Sorensen]

On Wed, Nov 01, 2023 at 09:27:16AM +, Modaresi Soft Hard wrote:
> Hello. From Debian 12 onwards, proprietary drivers will be automatically 
> installed in normal mode.
> 
> Can you make the installer ask questions in normal mode for installing 
> proprietary drivers?
> (Like a check box with No and Yes)
> 
> What does firmware=never do? # 
> https://wiki.debian.org/Firmware#How_to_disable_detection_and_use_of_non-free_firmware
> 
> Does firmware=never affect the installation and detection of free firmwares?
> 
> I use an interpreter. forgive me

firmware and proprietary drivers are two very different things.

Firmware files are loaded into memory on the hardware to make it operate.
The drivers are often still open source.  Proprietary drivers (like nvidia
and amd) on the other hand execute on your CPU, usually in kernel space
(at least partially) and is a very different story.  People tend to
have a much bigger issue with proprietary drivers than they do with
firmware files.

The firmware file simply does what in the past would have been done with
a rom or flash chip on the card but is now done with ram to save some
money on the design.

-- 
Len Sorensen

Add Feature Prevent Installing non-free-firmware in Noraml Mode (Like expert mode)

[Modaresi Soft Hard]

Hello. From Debian 12 onwards, proprietary drivers will be automatically 
installed in normal mode.

Can you make the installer ask questions in normal mode for installing 
proprietary drivers?
(Like a check box with No and Yes)

What does firmware=never do? # 
https://wiki.debian.org/Firmware#How_to_disable_detection_and_use_of_non-free_firmware

Does firmware=never affect the installation and detection of free firmwares?

I use an interpreter. forgive me

Bug#1050316: apt-setup: Unable to use local repo when installing older release

[Cyril Brulebois]

Hi Stephen,

Stephen Gelman  (2023-08-22):
> I understand that the current release is the main priority of d-i but
> given the fix seems to be low risk it would be appreciated if it could
> be fixed in stable!

Thanks for filing as suggested on IRC.

Given the conditions (oldstable as anticipated, but also: local
repository), I'd tend to agree with the “normal” severity, which doesn't
quite match the usual requirements for stable uploads…

We tend to have some leeway with the release team but I wouldn't want to
abuse it. Current gut feeling (after a minute or two only), would be
that it wouldn't deserve an upload on its own, but if there was some
other bugfixes we could probably lump it up in there.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1050316: apt-setup: Unable to use local repo when installing older release

[Stephen Gelman]

Source: apt-setup
Version: 1:0.183
Severity: normal
Tags: d-i
X-Debbugs-Cc: ssg...@debian.org

I sometimes use the current stable d-i to install the n-1 release when I
need to install on hardware that requires a newer kernel, then I install
the backport kernel in the preseed so the system boots. With the
bookworm debian-installer, my local apt repo does not get successfully
added to the system.

After some debugging, I determined the issue is here: 
https://salsa.debian.org/installer-team/apt-setup/-/blob/master/generators/60local#L46
The /etc/apt/keyrings directory wasn't added to the apt package until
apt 2.4.0, but bullseye only ships with 2.2.4. The fix here is simple
and I believe it to be low risk: the generator just needs to run
"mkdir -p /etc/apt/keyrings" at the beginning of 60local. Since newer
versions of apt already create that empty directory it will be a no-op
for them.

In case anyone else runs into this issue and stumbles onto this bug, I
was able to work around it by adding the following to my preseed:

d-i partman/early_command string printf "#!/bin/sh\nmkdir -p 
\$ROOT/etc/apt/keyrings\n" > /usr/lib/apt-setup/generators/02fixbug && chmod +x 
/usr/lib/apt-setup/generators/02fixbug

I understand that the current release is the main priority of d-i but
given the fix seems to be low risk it would be appreciated if it could
be fixed in stable!


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Roland Clobus]

Follow-up redirected to debian-live

Hello Sakkra Billa,

On 18/08/2023 15:27, Sakkra Billa wrote:
I followed the tutorial from: 
https://www.willhaley.com/blog/custom-debian-live-environment/ 


That tutorial is a summary/excerpt from 
https://live-team.pages.debian.net/live-manual/ to which it also points.


> ... Please guide me that where did i
> go wrong and how can i make my live iso installable.

I would recommend to use the live-build tool instead of doing each step 
manually. [1]


The official Debian 12 (Bookworm) live images are generated by 
live-build. If you want to extend your local version, I would recommend 
you to read [2] as well.


With kind regards,
Roland Clobus

[1] Disclaimer: I'm one of the maintainers of live-build, so I'm biased
[2] https://wiki.debian.org/ReproducibleInstalls/LiveImages


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Thomas Schmitt]

Hi,

Sakkra Billa wrote:
> In order to
> install it on my VM I installed calamares, calamares-settings-debian and
> rsync

My advise from debian-user to ask at debian-boot was rather a reply to
your other statement:

Sakkra Billa wrote:
> > I tried debian di too but wasn't successful in that
> > either it said that the kernel version for live and installer
> > were not the same.


Have a nice day :)

Thomas

Bootloader error grub minimal bash "load the kernel first" after installing my live image via calamares installer

[Sakkra Billa]

I followed the tutorial from:
https://www.willhaley.com/blog/custom-debian-live-environment/ to make a
live custom debian 12 image. In order to install it on my VM I installed
calamares, calamares-settings-debian and rsync . The live image works
perfectly and the installation also finishes without errors but when i
reboot my VM into the installed environment, it boots into grub minimal
bash line editing mode. On typing boot it says "load the kernel first".* I
did not change any of the calamares settings everything is default*. I
guess that i am missing some important files or applications required for
installation. Please guide me that where did i go wrong and how can i make
my live iso installable.
Thanks in advance,

Bug#1036659: installation-reports: LUKs Prompt Splash Screen and Console Prompt Disappears After Installing Nvidia Drivers

[Cyril Brulebois]

Control: reassign -1 nvidia-driver

Hi,

and thanks for your report.

Asmodean  (2023-05-23):
> Package: installation-reports
> Severity: normal
> X-Debbugs-Cc: place4...@gmail.com
> 
> (Please provide enough information to help the Debian
> maintainers evaluate the report efficiently - e.g., by filling
> in the sections below.)
> 
> Boot method: USB
> Image version: debian-bookworm-DI-rc3-amd64-DVD-1.iso
> Date: 05/23/23
> 
> Machine: i7-6700k, Nvidia 980 Ti, HDMI lik to monitor, 1080p monitor
> Partitions: `df -Tl`:
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% 
> /snapshots
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /swap
> /dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /var
> /dev/nvme0n1p2  ext2515668 80388409068  17% /boot
> /dev/nvme0n1p1  vfat54 11096511128   3% 
> /boot/efi
> /dev/mapper/sda1_crypt  btrfs488368128 380438904 107203864  79% /home
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:   [O]
> Detect network card:[O]
> Configure network:  [O]
> Detect media:   [O]
> Load installer modules: [O]
> Clock/timezone setup:   [O]
> User/password setup:[O]
> Detect hard drives: [O]
> Partition hard drives:  [O]
> Install base system:[O]
> Install tasks:  [O]
> Install boot loader:[O]
> Overall install:[O]
> 
> Comments/Problems:
> `initrd` was installed with the general option, and no extra modules
> were loaded when prompted to do so in the expert installer. After
> finishing the installation, the system rebooted correctly, albeit there
> being no splash screen for the LUKs prompt, only a console text prompt
> to enter the encryption passphrase. After decrypting everything and
> loading the graphical environment, i.e. XFCE, the `non-free` component was
> added to `/etc/apt/sources.list`, the package `linux-headers-amd64` was
> installed, and lastly the command `apt install nvidia-driver
> firmware-misc-nonfree` was run to install the proprietary Nvidia drivers
> for my GPU. At reboot time, bootloader GRUB appeared without problem,
> but after selecting the kernel and the initial loading that follows, the
> console only displayed the line "XDG something disabled" instead of
> showing the LUKs prompt. Though after waiting a few moments, supposedly
> for the keyboard modules to load, the passphrase can be entered without
> any visual feedback, with only the "XDG..." line on the screen. Pressing
>  following the passphrase boots the system into graphical target
> without problems. The questions are: 1. Why was the GUI splash screen 
> unavailable
>  after the reboot following installation?

That I don't know but I'm not going to consider a big issue. I've added
debian-xfce@ to cc so that they can give some feedback if they want to.

> 2. Why did the prompt disappear after
> installing Nvidia drivers? 3. Is there a way to fix this?
> Note: I installed the same system on the W550s Thinkpad which has a
> Nvidia GPU. The splash screen displayed correctly after pressing
>  following the initial boot, and loaded correctly too after
> installing the Nvidia drivers with identical steps detailed above. 

Reassigning to nvidia-driver for this part that seems much more
worrying.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#1036659: installation-reports: LUKs Prompt Splash Screen and Console Prompt Disappears After Installing Nvidia Drivers

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 nvidia-driver
Bug #1036659 [installation-reports] installation-reports: LUKs Prompt Splash 
Screen and Console Prompt Disappears After Installing Nvidia Drivers
Bug reassigned from package 'installation-reports' to 'nvidia-driver'.
Ignoring request to alter found versions of bug #1036659 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1036659 to the same values 
previously set

-- 
1036659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1036659: installation-reports: LUKs Prompt Splash Screen and Console Prompt Disappears After Installing Nvidia Drivers

[Asmodean]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: place4...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: debian-bookworm-DI-rc3-amd64-DVD-1.iso
Date: 05/23/23

Machine: i7-6700k, Nvidia 980 Ti, HDMI lik to monitor, 1080p monitor
Partitions: `df -Tl`:
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% 
/snapshots
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /swap
/dev/mapper/nvme0n1p3_crypt btrfs248993792  17590048 229590192   8% /var
/dev/nvme0n1p2  ext2515668 80388409068  17% /boot
/dev/nvme0n1p1  vfat54 11096511128   3% 
/boot/efi
/dev/mapper/sda1_crypt  btrfs488368128 380438904 107203864  79% /home


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
`initrd` was installed with the general option, and no extra modules
were loaded when prompted to do so in the expert installer. After
finishing the installation, the system rebooted correctly, albeit there
being no splash screen for the LUKs prompt, only a console text prompt
to enter the encryption passphrase. After decrypting everything and
loading the graphical environment, i.e. XFCE, the `non-free` component was
added to `/etc/apt/sources.list`, the package `linux-headers-amd64` was
installed, and lastly the command `apt install nvidia-driver
firmware-misc-nonfree` was run to install the proprietary Nvidia drivers
for my GPU. At reboot time, bootloader GRUB appeared without problem,
but after selecting the kernel and the initial loading that follows, the
console only displayed the line "XDG something disabled" instead of
showing the LUKs prompt. Though after waiting a few moments, supposedly
for the keyboard modules to load, the passphrase can be entered without
any visual feedback, with only the "XDG..." line on the screen. Pressing
 following the passphrase boots the system into graphical target
without problems. The questions are: 1. Why was the GUI splash screen 
unavailable
 after the reboot following installation? 2. Why did the prompt disappear after
installing Nvidia drivers? 3. Is there a way to fix this?
Note: I installed the same system on the W550s Thinkpad which has a
Nvidia GPU. The splash screen displayed correctly after pressing
 following the initial boot, and loaded correctly too after
installing the Nvidia drivers with identical steps detailed above. 


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20230515"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux 6700k 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 
(2023-05-08) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] 
(rev 07)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core 
Processor PCIe Controller (x16) [8086:1901] (rev 07)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD 
Graphics 530 [8086:1912] (rev 06)
lspci -knn: DeviceName:  Onboard IGD
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 
Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 100 
Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation 
Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] 
[8086:a102] (rev 31)
lspci -knn

Bug#693912: marked as done (cdrom path enabled when installing from usb)

[Debian Bug Tracking System]

Your message dated Mon, 24 Apr 2023 23:16:22 +0200
with message-id 
and subject line Re: Bug#693912: cdrom path enabled when installing from usb
has caused the Debian Bug report #693912,
regarding cdrom path enabled when installing from usb
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
693912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-setup
Severity: minor
Tags: d-i

when installing from a usb stick created by just copying the iso to the
raw device as described in manual section [4.3], from a weekly image
generated 2012-11-18, the sources.list file reads like this:

> # deb cdrom:[Debian GNU/Linux testing _Wheezy_ - Official Snapshot amd64 CD 
> Binary-1 20121113-01:23]/ wheezy main
> 
> deb cdrom:[Debian GNU/Linux testing _Wheezy_ - Official Snapshot amd64 CD 
> Binary-1 20121113-01:23]/ wheezy main

(among other lines). when the system starts up and the usb stick is left
plugged in, it is not discovered as a cdrom, though. (no wonder -- it
isn't one).

this is similar to bug #652987, but i don't know if its solution can
apply, as it refers to live system installations.

maybe instead of checking whether to disable the cd line, it could be
checked if an archive cd can be discovered (at install time), and only
then the line will be included?

[4.3] http://www.debian.org/releases/wheezy/amd64/ch04s03.html.en


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1:0.137

Hi,

chrysn  (2012-11-21):
> when installing from a usb stick created by just copying the iso to the
> raw device as described in manual section [4.3], from a weekly image
> generated 2012-11-18, the sources.list file reads like this:
> 
> > # deb cdrom:[Debian GNU/Linux testing _Wheezy_ - Official Snapshot amd64 CD 
> > Binary-1 20121113-01:23]/ wheezy main
> > 
> > deb cdrom:[Debian GNU/Linux testing _Wheezy_ - Official Snapshot amd64 CD 
> > Binary-1 20121113-01:23]/ wheezy main
> 
> (among other lines). when the system starts up and the usb stick is left
> plugged in, it is not discovered as a cdrom, though. (no wonder -- it
> isn't one).

If you look at the installer's log, you'll see that what happens during
installation was actually using that cdrom: source though. (Real CD or
DVD vs. image copied onto USB doesn't make a difference here, the ISO
ends up being mounted under /cdrom.)

> this is similar to bug #652987, but i don't know if its solution can
> apply, as it refers to live system installations.
> 
> maybe instead of checking whether to disable the cd line, it could be
> checked if an archive cd can be discovered (at install time), and only
> then the line will be included?

The netinst approach was extended to full CDs in:
  
https://salsa.debian.org/installer-team/apt-setup/-/commit/0627a0a26bc0643403db006ccaf0af91ea361d78


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

Problems faced while installing from debian-live iso and post-installation

[Susmita/Rajib]

Dear Leaders and senior list members of the Debian Universe with debian-boot.

I have an issue upon which I would like to draw your kind attention upon.

I had downloaded a live iso almost two years back (17th March 2021),
debian-live-10.8.0-amd64-lxde.iso.

While it used lxde in the live mode, when installed on the HDD it
presented a Unity desktop environment which is not as easy as lxde,
with which I have been familiar for more than a decade because of
Knoppix and ease.

My findings:

I used a specific Live image is used to write a flash drive from the
appropriate page. Choose a specific Live OS image from
https://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/. In
that case, we could be able to install the Desktop Environment of our
choice.

I tried to install this way, but the spoilsport is Debian installer's
internet configuration. It still sticks with DHCP interface (using a
LAN cable) whereas we in India also use high speed 4G and 5G mobile
networks using our mobiles, dongles, smartphones, etc., but use the
data + charging USB cable with these gadgets, not LAN cables. I tried
but Debian installer wasn't able to configure the internet connection
using the USB port.

Of course, I have observed that when the OS is set up on the HDD, then
the same data connection could be used with a USB cable and the mobile
phone, but the OS run from the Live Flash drive can't configure the
internet with the said set up.

So please advise me and also help in the matter being taken up with
the Debian OS installer team? So that a breakthrough be informed me on
how to configure the USB data cable for the installer to access the
internet and set up the OS on the HDD?

Since I used the lxde live iso image but got a Unity Desktop
environment, there must be a trick to get back to the usual and known
lxde environment with old menu driven User Interface. Could I also be
helped in this regard please?

Best wishes,
Rajib Bandopadhyay
A dedicated user of Debian/Knoppix

Bug#969516: Please support installing onto f2fs root filesystem

[Stuart]

Is there any update to this? I can't find the source anywhere to test it
myself either.

Bug#951198: flash-kernel: prevents installing new kernels on unsupported platforms

[Pirate Praveen]

On Wed, 12 Feb 2020 12:09:19 +0100 =?utf-8?q?Uwe_Kleine-K=C3=B6nig?=
 wrote:
> Package: flash-kernel
> Version: 3.99
> Severity: normal
> 
> Hello,
> 
> I just upgraded my Debian installation from an older testing to
Buster
> and the kernel update failed with:
> 
>   Setting up initramfs-tools (0.133+deb10u1) ...
>   update-initramfs: deferring update (trigger activated)
>   Processing triggers for initramfs-tools (0.133+deb10u1) ...
>   update-initramfs: Generating /boot/initrd.img-4.16.0-2-armmp
>   Unsupported platform.
>   run-parts: /etc/initramfs/post-update.d//flash-kernel exited
with return code 1
>   dpkg: error processing package initramfs-tools (--configure):
>    installed initramfs-tools package post-installation script
subprocess returned error exit status 1
>   Errors were encountered while processing:
>    initramfs-tools
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> In my case flash-kernel is just casually installed and not needed to
> make the machine bootable with the new kernel. I wonder if
"Unsupported
> platform" should not be an error in the kernel update trigger.
> 
> Best regards
> Uwe

I also noticed this error when trying to update a kernel from a
recovery chroot (using jumpdrive) on my Librem 5.
https://github.com/dreemurrs-embedded/Jumpdrive/issues/79

This is just annoying as it did not really affect booting of the
machine.

Bug#1023448: installation-reports: Hash sum mismatch when installing linux-image

[Peter Nagel]

Package: installation-reports

Boot method: USB stick
Image version: 
https://cdimage.debian.org/cdimage/bookworm_di_alpha1/amd64/iso-cd/debian-bookworm-DI-alpha1-amd64-netinst.iso

Date: 03.11.2022

Machine: Standard PC
Processor: Core i7-11700 @ 2.50 GHz
Memory: 64 GB
Partitions:
/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Hitachi HDS72101
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C338BFE6-3B2F-40EB-B8A9-62B73D82B37B

Device Start    End   Sectors Size Type
/dev/sda1   2048   4095  2048 1M Linux filesystem
/dev/sda2   4096   97660927  97656832 46.6G Linux filesystem
/dev/sda3   97660928  195317759  97656832 46.6G Linux filesystem
/dev/sda4  195317760  205082623   9764864 4.7G Linux swap
/dev/sda5  205082624 1083987967 878905344 419.1G Linux filesystem

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4c43] (rev 01)
00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:4c01] (rev 01)
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:43ed] (rev 11)
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:43ef] (rev 11)
00:16.0 Communication controller [0780]: Intel Corporation Device 
[8086:43e0] (rev 11)
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] 
(rev 11)

00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:43c4] (rev 11)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:43bc] (rev 11)
00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:43b0] (rev 11)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:4387] (rev 11)
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:43c8] (rev 11)
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:43a3] (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 
[8086:43a4] (rev 11)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU107 
[10de:1f82] (rev a1)

01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:10fa] (rev a1)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] 
(rev 16)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:    [O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:    [E]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:  [ ]
Install boot loader:    [ ]
Overall install:    [ ]

Comments/Problems:
The image was copied to USB-Stick via:  cp  /dev/sdb
The Debian installation was performed on partition /dev/sda2
Expecting that kernel 6.0 is installed.
When trying to install the base system (linux-image) a hash sum mismath 
occurs - see syslog below:


Nov  3 08:06:08 in-target: Selecting previously unselected package 
initramfs-tools.^M
Nov  3 08:06:08 in-target: Preparing to unpack 
.../initramfs-tools_0.142_all.deb ...^M

Nov  3 08:06:08 in-target: Unpacking initramfs-tools (0.142) ...^M
Nov  3 08:06:09 in-target: Setting up linux-base (4.9) ...^M
Nov  3 08:06:09 in-target: Setting up libklibc:amd64 (2.0.10-4) ...^M
Nov  3 08:06:09 in-target: Setting up klibc-utils (2.0.10-4) ...^M
Nov  3 08:06:09 in-target: No diversion 'diversion of 
/usr/share/initramfs-tools/hooks/klibc to 
/usr/share/initramfs-tools/hooks/klibc^i-t by klibc-utils', no

ne removed.^M
Nov  3 08:06:09 in-target: Setting up initramfs-tools-core (0.142) ...^M
Nov  3 08:06:09 in-target: Setting up initramfs-tools (0.142) ...^M
Nov  3 08:06:10 in-target: update-initramfs: deferring update (trigger 
activated)^M
Nov  3 08:06:10 in-target: Processing triggers for initramfs-tools 
(0.142) ...^M
Nov  3 08:06:11 base-installer: dpkg-divert: warning: diverting file 
'/sbin/start-stop-daemon' from an Essential package with rename is 
dangerous, use --no-re

name
Nov  3 08:06:11 /bin/in-target: warning: /target/etc/mtab won't be 
updated since it is a symlink.

Nov  3 08:06:12 in-target: Reading package lists...
Nov  3 08:06:12 in-target:
Nov  3 08:06:12 in-target: Building dependency tree...
Nov  3 08:06:12 in-target:
Nov  3 08:06:12 in-target: Reading state information...
Nov  3 08:06:12 in-target: The following additional packages will be 
installed:
Nov  3 08:06:12 in-target:   apparmor firmware-linux-free 
linux-image-5.19.0-1-amd64

Nov  3 08:06:12 in-target: Suggested packages:
Nov  3 08:06:12 in-target: apparmor-profiles-extra apparmor-utils 
linux-doc-5.19 debian-kernel-handbook

Nov  3 08:06:12 in-target:   grub-pc | grub-efi-amd64 | extlinux
Nov  3 08:06:12 in-target: The following NEW packages will be installed:
Nov  3 08:06:12 in-target:   apparmor firmware-linux-free 
linux-image-5.19.0-1-amd64 linux

Bug#926699: marked as done (libc6 foreign/biarch: installing, removing, reinstalling in a --merged-usr system results in unmerged /lib{32,x32})

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2022 23:12:19 +
with message-id 
and subject line Bug#926699: fixed in glibc 2.35-1
has caused the Debian Bug report #926699,
regarding libc6 foreign/biarch: installing, removing, reinstalling in a 
--merged-usr system results in unmerged /lib{32,x32}
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
926699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-x32,libc6-i386
Version: 2.28-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts in a --merged-usr environment I noticed that
installing, removing, and installing again a package shipping /lib32,
/libx32 will actually unmerge that directory.
The package will take ownership of the preexisting symlinks
/lib{32,x32} -> /usr/lib{32,x32} that were created by debootstrap,
remove them and create plain /usr/lib{32,x32} directories in the next
installation.
(/lib64 should be mostly safe due to /lib64/ld-linux-x86-64.so.2, but
perhaps on !x86 architectures)

The preinst scripts could check whether the package is being installed
in a --merged-usr environment and create (dangling) symlinks if
/usr/lib{32,x32} is missing. And postrm remove could recreate them if
they went missing.

Andreas
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.35-1
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 22 Sep 2022 22:02:00 +0200
Source: glibc
Architecture: source
Version: 2.35-1
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 926699
Changes:
 glibc (2.35-1) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-strerror_X.diff: Fix tst-sprintf-errno test.
   * debian/patches/hurd-i386/git-readlink-fifo.diff: Fix readlink() on fifos.
   * debian/patches/hurd-i386/git-net-route.h.diff: Add ifrtreq structure and
 fix SIOCADD/DELRT ioctls.
   * debian/patches/hurd-i386/submitted-net.diff: Drop net/route.h part.
 .
   [ Aurelien Jarno ]
   * debian/control.in/main: add a breaks against dh-lua (<< 27+nmu1~) to
 libc-bin. See #1017832.
   * debian/patches/git-updates.diff: update from upstream stable branch.
   * debian/rules.d/build.mk: fix the pt_chown permissions after installation
 when running with Rules-Requires-Root=no (for non-Linux systems).
   * debian/control.in/main: set Rules-Requires-Root: no.
   * debian/debhelper.in/libc.preinst: only apply NSS workaround when upgrading
 from glibc < 2.34.
   * debian/patches/git-updates.diff: update from upstream stable branch.
 .
   [ Luca Boccassi ]
   * debian/debhelper.in/libc-alt.preinst: libc6-: create merged-usr
 symlinks via preinst script.  Closes: #926699.
 .
   [ Gioele Barabucci ]
   * debian/debhelper.in/libc.preinst: avoid using pidof.
Checksums-Sha1:
 a2b972e42c6641fff2c670d16d40ad2a522fe8dd 9679 glibc_2.35-1.dsc
 ca29d5e10a5e1c697b5dce8f7d13c76269c1a383 916928 glibc_2.35-1.debian.tar.xz
 d08b48c2de1eb72687e475d7b9f352aa9dbc3531 9567 glibc_2.35-1_source.buildinfo
Checksums-Sha256:
 923452fa13678ff2b8a20221b22eb9d4e654938cda3ccda355fb3a37b5a763a8 9679 
glibc_2.35-1.dsc
 a1b9ee28791d2a512d9835ea5d8bd8b5d246fb2a2fadb8e92e9e7f5222801517 916928 
glibc_2.35-1.debian.tar.xz
 9461deae10eed7835b6bf2cfb48398fcc1d4146c035b17412d1b44b080ac3ddc 9567 
glibc_2.35-1_source.buildinfo
Files:
 5cbca35aea4c50dbbdd9e3fb3266d1f8 9679 libs required glibc_2.35-1.dsc
 e6e6a855562ccd1c17c8658832c93121 916928 libs required 
glibc_2.35-1.debian.tar.xz
 4284051ed17149929eec52d5c7afc077 9567 libs required 
glibc_2.35-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmMswJcACgkQE4jA+Jno
M2sMWA//dDWNXCspDgfNHvojIJ7/qvbLOXBbegLBzslcVL/m61gv

Processed: Re: Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 apt-setup-udeb
Bug #1015887 [debian-installer] debian-installer: Adding https repo doesn't 
work without manually installing ca-certificates
Bug reassigned from package 'debian-installer' to 'apt-setup-udeb'.
Ignoring request to alter found versions of bug #1015887 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1015887 to the same values 
previously set
> fixed -1 1:0.169
Bug #1015887 [apt-setup-udeb] debian-installer: Adding https repo doesn't work 
without manually installing ca-certificates
Marked as fixed in versions apt-setup/1:0.169.

-- 
1015887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Philip Hands]

Control: reassign -1 apt-setup-udeb
Control: fixed -1 1:0.169

Hi,

I just had a look at this, and it seems to me that this was fixed in
apt-setup-udeb 0.169, but the version in the released (Debian 11)
installer is only at 0.166, so does not include the fix.

Looking at the syslog in this bug, one can see:

  apt-setup-udeb 1:0.166

which is the version in the release, and is from 2021-07-23.

The thing that fixes the bug is:

  https://salsa.debian.org/installer-team/apt-setup/-/merge_requests/4

which was merged on 2022-01-29, then released as part of 1:0.169.

I've reproduced the failure with the release version of D-I, and failed
to reproduce it with yesterday's daily image (where one sees the
installation of the c-certificates package go past just after selecting
the mirror), so it really looks to have been fixed already.

If you want to try that for yourself, the daily images can be found
here:

  
https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY

Bug#1019569: Installing with USB, don't use USB3 port.

[Pascal Hambourg]

Hello,

On 12/09/2022 at 10:47, KNE wrote:


Boot method: USB stick to Network
Image version: debian-11.5.0-amd64-netinst.iso 


(...)

Comments/Problems: don’t know if this has been mentioned or not, but while 
trying install the USB kept changing mount points, it started at sdg,sdh,sdi 
all the way up to sdo, which would error the install.


These are device names, not mount points.


Install kept saying to put the install media into /media/cdrom.  I finally 
figured out that the USB was plugged into a USB3 slot, once I moved it to a 
regular USB the install worked great.


Sounds like a xHCI driver/controller/port/connector/stick issue causing 
endless disconnects/reconnects. Please check the kernel logs.

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Cyril Brulebois]

Richard Hector  (2022-07-24):
> Oh - uncompressed, it made it into the BTS, but not to the list. Here's a
> compressed version.

Thanks.

debootstrap uses the ISO's contents, so https isn't noticed at this point
(final argument):

Jul 23 01:03:18 debootstrap: /usr/sbin/debootstrap --components=main 
--debian-installer --resolve-deps --no-check-gpg bullseye /target file:///cdrom/

Later:

Jul 23 01:07:13 apt-setup: Identifying...
Jul 23 01:07:13 apt-setup: [5f70f43faa4e30b11b269f8c73178e29-2]
Jul 23 01:07:13 apt-setup: Scanning disc for index files...
Jul 23 01:07:13 apt-setup: Found 1 package indexes, 0 source indexes, 1 
translation indexes and 0 signatures
Jul 23 01:07:13 apt-setup: This disc is called:
Jul 23 01:07:13 apt-setup: 'Debian GNU/Linux 11.4.0 _Bullseye_ - Official 
amd64 NETINST 20220709-10:31'
Jul 23 01:07:13 apt-setup: Copying package lists...
Jul 23 01:07:13 apt-setup: ^MReading Package Indexes... 0%^M
Jul 23 01:07:13 apt-setup: ^MReading Package Indexes... 0%^M
Jul 23 01:07:13 apt-setup: ^MReading Package Indexes... Done^M
Jul 23 01:07:13 apt-setup: ^MReading Translation Indexes... 0%^M
Jul 23 01:07:13 apt-setup: ^MReading Translation Indexes... Done^M
Jul 23 01:07:13 apt-setup: Writing new source list
Jul 23 01:07:13 apt-setup: Source list entries for this disc are:
Jul 23 01:07:13 apt-setup: deb cdrom:[Debian GNU/Linux 11.4.0 _Bullseye_ - 
Official amd64 NETINST 20220709-10:31]/ bullseye main
Jul 23 01:07:13 apt-setup: Repeat this process for the rest of the CDs in 
your set.
Jul 23 01:07:45 choose-mirror[24148]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/bullseye/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Jul 23 01:07:45 choose-mirror[24148]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian/dists/stable/Release -O - | grep -E 
'^(Suite|Codename|Architectures):'
Jul 23 01:07:46 choose-mirror[24148]: INFO: suite/codename set to: 
stable/bullseye
Jul 23 01:07:46 choose-mirror[24148]: DEBUG: command: wget --no-verbose 
https://deb.debian.org/debian//dists/bullseye/main/binary-amd64/Release -O - | 
grep ^Architecture:
Jul 23 01:08:12 apt-setup: dpkg-divert: warning: diverting file 
'/sbin/start-stop-daemon' from an Essential package with rename is dangerous, 
use --no-rename
Jul 23 01:08:13 in-target: Err:1 https://deb.debian.org/debian bullseye 
InRelease
Jul 23 01:08:13 in-target:   Certificate verification failed: The 
certificate is NOT trusted. The certificate issuer is unknown.  Could not 
handshake: Error in the certificate verification. [IP: 2a04:4e42:27::644 443]

I think the choose-mirror calls come from apt-setup's generators/50mirror
(after generators/40cdrom and generators/41cdset), and that one is supposed
to know about ca-certificates:
  
https://salsa.debian.org/installer-team/apt-setup/-/blob/master/generators/50mirror#L233-245

I suppose the in-target calls might be from apt-setup-verify, called later:
  
https://salsa.debian.org/installer-team/apt-setup/-/blob/master/generators/50mirror#L264

If you want to help troubleshoot that further, checking the debconf
exchanges could be interesting. I think we support setting
DEBCONF_DEBUG=developer on the kernel command line, which should make
debconf queries/answers (as triggered by db_get and friends) appear in the
syslog. Past $self seems to agree:
  https://mraw.org/blog/2012/12/23/d-i_hacking_recipe_3/


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Geert Stappers]

On Sun, Jul 24, 2022 at 12:15:24AM +1200, Richard Hector wrote:
> On 23/07/22 23:01, Cyril Brulebois wrote:
> 
> > As mentioned by Julien, getting the installer's syslog (compressed, to
> > make sure it reaches the mailing list) would help understand what's
> > going on.
> 
> Oh - uncompressed, it made it into the BTS,
 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1015887;filename=syslog;msg=27

Jul 23 01:08:13 in-target: Err:1 https://deb.debian.org/debian bullseye 
InRelease
Jul 23 01:08:13 in-target:   Certificate verification failed: The certificate 
is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error 
in the certificate verification. [IP: 2a04:4e42:27::644 443]
Jul 23 01:08:13 in-target: Reading package lists...
Jul 23 01:08:13 in-target: 
Jul 23 01:08:13 in-target: W: 
https://deb.debian.org/debian/dists/bullseye/InRelease: No system certificates 
available. Try installing ca-certificates.
Jul 23 01:08:13 in-target: W: Failed to fetch 
https://deb.debian.org/debian/dists/bullseye/InRelease  Certificate 
verification failed: The certificate is NOT trusted. The certificate issuer is 
unknown.  Could not handshake: Error in the certificate verification. [IP: 
2a04:4e42:27::644 443]
Jul 23 01:08:13 in-target: W: Some index files failed to download. They have 
been ignored, or old ones used instead.
Jul 23 01:08:13 apt-setup: dpkg-divert: warning: diverting file 
'/sbin/start-stop-daemon' from an Essential package with rename is dangerous, 
use --no-rename
Jul 23 01:08:14 in-target: Err:1 https://deb.debian.org/debian bullseye 
InRelease
Jul 23 01:08:14 in-target:   Certificate verification failed: The certificate 
is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error 
in the certificate verification. [IP: 2a04:4e42:27::644 443]
Jul 23 01:08:14 in-target: Reading package lists...
Jul 23 01:08:14 in-target: 
Jul 23 01:08:14 in-target: W: 
https://deb.debian.org/debian/dists/bullseye/InRelease: No system certificates 
available. Try installing ca-certificates.
Jul 23 01:08:14 in-target: W: Failed to fetch 
https://deb.debian.org/debian/dists/bullseye/InRelease  Certificate 
verification failed: The certificate is NOT trusted. The certificate issuer is 
unknown.  Could not handshake: Error in the certificate verification. [IP: 
2a04:4e42:27::644 443]
Jul 23 01:08:14 in-target: W: Some index files failed to download. They have 
been ignored, or old ones used instead.


no traces of manual install of ca-certificates found by me.


Regards
Geert Stappers
Failed to explain that httpS is NOT needed for apt.
Agrees that it is nice to have ca-certificates installed.
-- 
Silence is hard to parse

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Richard Hector]

On 23/07/22 23:01, Cyril Brulebois wrote:


As mentioned by Julien, getting the installer's syslog (compressed, to
make sure it reaches the mailing list) would help understand what's
going on.


Oh - uncompressed, it made it into the BTS, but not to the list. Here's 
a compressed version.


Cheers,
Richard

syslog.gz
Description: application/gzip

Processed: Re: Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1015887 [debian-installer] debian-installer: Adding https repo doesn't 
work without manually installing ca-certificates
Severity set to 'important' from 'wishlist'

-- 
1015887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Cyril Brulebois]

Control: severity -1 important

Richard Hector  (2022-07-23):
> On 23/07/22 18:07, Geert Stappers wrote:
> > Control: severity -1 wishlist
> 
> Why? Because there's a workaround? Is everyone expected to be able to find
> that workaround?
> 
> https is an option provided in the installer, that apparently doesn't work
> (at least with the netinst installer), and it's not immediately clear why.

That's definitely something that ought to work, fixing severity.

(I do test installation using HTTPS for all releases, even if that's
using the netboot-gtk mini.iso, seeding repository parameters via the
kernel command line; so HTTPS support should not be *horribly* broken.)

We even have code to install apt-transport-https conditionally (since
that feature was merged into apt proper a while back), see:
  
https://salsa.debian.org/installer-team/debootstrap/-/blob/master/scripts/debian-common#L30-42

I remember having to patch a few components to make sure it would work
for all installation images, when support was implemented in the first
place.

As mentioned by Julien, getting the installer's syslog (compressed, to
make sure it reaches the mailing list) would help understand what's
going on.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Julien Cristau]

On Sat, Jul 23, 2022 at 03:49:55PM +1200, Richard Hector wrote:
> Package: debian-installer
> Severity: important
> 
> Dear Maintainer,
> 
> Using netinst bullseye 11.4 installer:
> 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.4.0-amd64-netinst.iso
> 
> I chose to add a network mirror, using https, and the default
> 'deb.debian.org'.
> 
> I used (non-graphical) Expert Mode.
> 
> The problem first showed up when tasksel only displayed 'standard system
> utilities'. When I went ahead with that, the next screen was a red
> 'Installation step failed' screen.
> 
> The log on tty4 showed various dependency problems.
> 
> I tried to 'chroot /target' and 'apt update', which showed certificate
> problems. I then ran 'apt install ca-certificates', which worked
> (installing from the cd image?), after which 'apt update' worked, and I
> was also able to continue successfully with the installer.
> 
> I was able to reproduce this in a (kvm/qemu) VM (which is where I
> confirmed my steps); the original problem was on an HP Thin Client
> (t520). In both cases only 8G of storage was available.
> 
> It all works fine using http for the mirror.
> 
> I'm happy to do further testing with the VM; the thin client is less
> convenient as it has a job to do.
> 
Please attach syslog from the installer.

Cheers,
Julien

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Richard Hector]

On 23/07/22 18:07, Geert Stappers wrote:

Control: severity -1 wishlist


Why? Because there's a workaround? Is everyone expected to be able to 
find that workaround?


https is an option provided in the installer, that apparently doesn't 
work (at least with the netinst installer), and it's not immediately 
clear why.


Essentially, I think it's a showstopper for anyone who doesn't know how 
to investigate further.



It all works fine using http for the mirror.


And the archive mirror content is secured by checksums and signatures.


The point being that https isn't necessary? A different issue, I think.


I'm happy to do further testing with the VM; the thin client is less
convenient as it has a job to do.


Another job that will help: Find other bug reports that ask for installing
ca-certificates.  Yeah, I recall have I seen such requests before.


Not sure how to do that. The BTS UI doesn't seem to allow searching on 
the content of bug discussions; only subject and other metadata. I can't 
see any other debian-installer bugs that mention ca-certificates in the 
subject.


Cheers,
Richard

Processed: Re: Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #1015887 [debian-installer] debian-installer: Adding https repo doesn't 
work without manually installing ca-certificates
Severity set to 'wishlist' from 'important'

-- 
1015887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Geert Stappers]

Control: severity -1 wishlist

On Sat, Jul 23, 2022 at 03:49:55PM +1200, Richard Hector wrote:
> Dear Maintainer,
> 
> Using netinst bullseye 11.4 installer:
> 
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.4.0-amd64-netinst.iso
> 
> I chose to add a network mirror, using https, and the default
> 'deb.debian.org'.
> 
> I used (non-graphical) Expert Mode.
> 
> The problem first showed up when tasksel only displayed 'standard system
> utilities'. When I went ahead with that, the next screen was a red
> 'Installation step failed' screen.
> 
> The log on tty4 showed various dependency problems.
> 
> I tried to 'chroot /target' and 'apt update', which showed certificate
> problems. I then ran 'apt install ca-certificates', which worked
> (installing from the cd image?), after which 'apt update' worked, and I
> was also able to continue successfully with the installer.
> 
> I was able to reproduce this in a (kvm/qemu) VM (which is where I
> confirmed my steps); the original problem was on an HP Thin Client
> (t520). In both cases only 8G of storage was available.
> 
> It all works fine using http for the mirror.

And the archive mirror content is secured by checksums and signatures.

 
> I'm happy to do further testing with the VM; the thin client is less
> convenient as it has a job to do.

Another job that will help: Find other bug reports that ask for installing
ca-certificates.  Yeah, I recall have I seen such requests before.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Bug#1015887: debian-installer: Adding https repo doesn't work without manually installing ca-certificates

[Richard Hector]

Package: debian-installer
Severity: important

Dear Maintainer,

Using netinst bullseye 11.4 installer:

https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.4.0-amd64-netinst.iso

I chose to add a network mirror, using https, and the default
'deb.debian.org'.

I used (non-graphical) Expert Mode.

The problem first showed up when tasksel only displayed 'standard system
utilities'. When I went ahead with that, the next screen was a red
'Installation step failed' screen.

The log on tty4 showed various dependency problems.

I tried to 'chroot /target' and 'apt update', which showed certificate
problems. I then ran 'apt install ca-certificates', which worked
(installing from the cd image?), after which 'apt update' worked, and I
was also able to continue successfully with the installer.

I was able to reproduce this in a (kvm/qemu) VM (which is where I
confirmed my steps); the original problem was on an HP Thin Client
(t520). In both cases only 8G of storage was available.

It all works fine using http for the mirror.

I'm happy to do further testing with the VM; the thin client is less
convenient as it has a job to do.

-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-16-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Re: Debian not bootable after installing Ubuntu

[Lennart Sorensen]

On Wed, Apr 06, 2022 at 12:19:50PM -0400, Jeremy Bicha wrote:
> Hi,
> 
> I'm emailing this list because I didn't know a more specific place to
> report this bug.
> 
> What I Did
> --
> - I used GNOME Boxes 42 (from my Ubuntu 22.04 LTS host).
> - I clicked + then Download an Operating System and chose Debian Testing.
> - I believe this uses
> https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
> and
> https://salsa.debian.org/libvirt-team/osinfo-db/-/blob/debian/sid/data/install-script/debian.org/debian-preseed-desktop.xml.in
> - I increased the virtual disk size a bit on the confirm prompt (to like 25 
> GB)
> - That install worked and I got a functioning Debian GNOME Testing install.
> 
> - Then I used today's daily build of Ubuntu 22.04 (pre-release) to
> install Ubuntu.
> - It resized the Debian partition and I had to manually tweak it just
> a bit to get a big enough partition for Ubuntu alongside Debian.
> - After installing Ubuntu, there was a Debian option in the grub boot
> menu installed by Ubuntu.
> - Debian failed to boot. I'm attaching a screenshot. It says:
> error: bad shim signature.
> error: you need to load the kernel first.
> 
> Maybe this is as easy as telling osinfo-db to also install a signed
> kernel. Maybe the signing thing is more complicated. I'm not really
> going to spend more time on this issue but I wanted to pass it along
> so that someone else who is interested could try to fix it.

Sounds like you installed debian with secureboot enabled, and then
installed ubuntu which replaced the boot loader which of course breaks
the secureboot chain of trust and it correctly identified the tampering
and prevented the boot of an insecure temperated environment.

I could be wrong.  I personally don't use secureboot on my systems.

-- 
Len Sorensen

Debian not bootable after installing Ubuntu

[Jeremy Bicha]

Hi,

I'm emailing this list because I didn't know a more specific place to
report this bug.

What I Did
--
- I used GNOME Boxes 42 (from my Ubuntu 22.04 LTS host).
- I clicked + then Download an Operating System and chose Debian Testing.
- I believe this uses
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
and
https://salsa.debian.org/libvirt-team/osinfo-db/-/blob/debian/sid/data/install-script/debian.org/debian-preseed-desktop.xml.in
- I increased the virtual disk size a bit on the confirm prompt (to like 25 GB)
- That install worked and I got a functioning Debian GNOME Testing install.

- Then I used today's daily build of Ubuntu 22.04 (pre-release) to
install Ubuntu.
- It resized the Debian partition and I had to manually tweak it just
a bit to get a big enough partition for Ubuntu alongside Debian.
- After installing Ubuntu, there was a Debian option in the grub boot
menu installed by Ubuntu.
- Debian failed to boot. I'm attaching a screenshot. It says:
error: bad shim signature.
error: you need to load the kernel first.

Maybe this is as easy as telling osinfo-db to also install a signed
kernel. Maybe the signing thing is more complicated. I'm not really
going to spend more time on this issue but I wanted to pass it along
so that someone else who is interested could try to fix it.

Thank you,
Jeremy Bicha

Re: Possible to force installing from the mirror instead of the installation media?

[Andrew M.A. Cater]

On Mon, Feb 21, 2022 at 06:19:30PM +0800, Glen Huang wrote:
> @Geert
> > It is "netinst" that you are looking for.
> 
> I am using netinst. Appreciate the detailed steps listed, but with all
> due respect, my question was about how to make the installer install
> the base system from the mirror and not the installation media. The
> listed steps don't seem to help with that.
> 
> @Andrew @Holger @Steve
> I take that as it's not possible to force the installer to install the
> base system from the mirror? I guess the netboot image probably does
> something special.
> 
> Guess I'll just have to let the installer upgrade then.
> 
> @Andrew
> > an autoremove would remove the fallback kernel since you didn't boot from it
> 
> I'm not sure that's the case. I tried running "apt-get autoremove" in
> a newly installed Debian 11 with multiple kernels in /boot, no
> packages got removed. `apt-cache rdepends --installed
> linux-image-5.10.0-10-amd64` (which was the old kernel) showed
> "linux-image-amd64" depended on it, so it was not removed. "apt-cache
> depends --installed linux-image-amd64" showed it depended on
> "linux-image-5.10.0-11-amd64".
> 
> Regards,
> Glen
>

Netboot provides you a base kernel, an initrd and enough of the installer to 
start from there.

The netinst / DVD includes the base systme on it - but will still update
if packages are newer on the mirror.

All the very best, as ever,

Andy Cater 

Re: Possible to force installing from the mirror instead of the installation media?

[Samuel Thibault]

Glen Huang, le lun. 21 févr. 2022 18:19:30 +0800, a ecrit:
> @Geert
> > It is "netinst" that you are looking for.
> 
> I am using netinst. Appreciate the detailed steps listed, but with all
> due respect, my question was about how to make the installer install
> the base system from the mirror and not the installation media. The
> listed steps don't seem to help with that.

You can use netboot, which does not have any .deb file.

Samuel

Re: Possible to force installing from the mirror instead of the installation media?

[Glen Huang]

@Geert
> It is "netinst" that you are looking for.

I am using netinst. Appreciate the detailed steps listed, but with all
due respect, my question was about how to make the installer install
the base system from the mirror and not the installation media. The
listed steps don't seem to help with that.

@Andrew @Holger @Steve
I take that as it's not possible to force the installer to install the
base system from the mirror? I guess the netboot image probably does
something special.

Guess I'll just have to let the installer upgrade then.

@Andrew
> an autoremove would remove the fallback kernel since you didn't boot from it

I'm not sure that's the case. I tried running "apt-get autoremove" in
a newly installed Debian 11 with multiple kernels in /boot, no
packages got removed. `apt-cache rdepends --installed
linux-image-5.10.0-10-amd64` (which was the old kernel) showed
"linux-image-amd64" depended on it, so it was not removed. "apt-cache
depends --installed linux-image-amd64" showed it depended on
"linux-image-5.10.0-11-amd64".

Regards,
Glen

Re: Possible to force installing from the mirror instead of the installation media?

[Steve McIntyre]

On Mon, Feb 21, 2022 at 09:53:42AM +0100, Holger Wansing wrote:
>Hi,
>
>Am 21. Februar 2022 05:05:53 MEZ schrieb Glen Huang :
>>I wonder if it's possible to force the installer to use the mirror for
>>installing the base system?
>
>Yes, there's a solution for this:
>just use the netboot image :-)
>
>I guess this is the most obvious answer for such question.

Yup, exactly.

One of the main points of including the base system on bigger media is
to have it all available there as a consistent set...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?

Re: Possible to force installing from the mirror instead of the installation media?

[Holger Wansing]

Hi,

Am 21. Februar 2022 05:05:53 MEZ schrieb Glen Huang :
>I wonder if it's possible to force the installer to use the mirror for
>installing the base system?

Yes, there's a solution for this:
just use the netboot image :-)

I guess this is the most obvious answer for such question.

Holger


-- 
Sent from /e/ OS on Fairphone3

Re: Possible to force installing from the mirror instead of the installation media?

[Andrew M.A. Cater]

On Mon, Feb 21, 2022 at 12:05:53PM +0800, Glen Huang wrote:
> Hi,
> 
> I remember reading it somewhere in a Debian doc (though I can no
> longer find it) that only netboot automatically installs the base
> system from a mirror, other media install from the media itself and
> then upgrade via the mirror if allowed.
> 
> I wonder if it's possible to force the installer to use the mirror for
> installing the base system? Currently, my installer installs two
> versions of kernels, one from the media, the other from upgrading via
> the mirror, which seems like a waste.
> 

This is intended behaviour, in some sense. If you install from DVD / other
media, as soon as it reaches a mirror, it will update from the package list
there - and, in fact, you often see it updating packages in the course of
the install at that point. That ensures that you're up to date at the
point you touch a mirror so that you don't have to apt-get update or 
whatever immediately afterwards.

This can cause problems if there is a kernel ABI bump or whatever and your
netboot kernel has changed significantly on the mirror (if your netinst
is too old / you're tracking dailies from testing, for example) but that's
an acceptable situation, I think. It nromally resolves quickly - or by
using an up to date netboot.

On first reboot, the newest kernel will be used anyway: an autoremove
would remove the fallback kernel since you didn't boot from it, if you
wished to do that.

> I couldn't find the preseed directive that controls this. Would be
> grateful if someone could shed some light.
> 
> Regards,
> Glen
> 

All best, as ever,

Andrew Cater

Re: Possible to force installing from the mirror instead of the installation media?

[Geert Stappers]

On Mon, Feb 21, 2022 at 12:05:53PM +0800, Glen Huang wrote:
> Hi,
> 
> I remember reading it somewhere in a Debian doc (though I can no
> longer find it) that only netboot automatically installs the base
> system from a mirror, other media install from the media itself and
> then upgrade via the mirror if allowed.
> 
> I wonder if it's possible to force the installer to use the mirror for
> installing the base system? Currently, my installer installs two
> versions of kernels, one from the media, the other from upgrading via
> the mirror, which seems like a waste.
> 
> I couldn't find the preseed directive that controls this.

:-)



Visit https://www.debian.org with a recent webbrowser
Click "download" to go to https://www.debian.org/download
Qouting that page:

  Thank you for downloading Debian!

  This is Debian 11, codenamed bullseye, netinst, for 64-bit PC (arch).

  If your download does not start automatically, click 
debian-11.2.0-arch-netinst.iso.

  Download checksum: SHA512SUMS Signature


The page presents also downloading debian-11.2.0-arch-netinst.iso.


> Would be grateful if someone could shed some light.

It is "netinst" that you are looking for.
At https://www.debian.org/distrib/ is that documented.
Page https://www.debian.org/download has the "distrib page" linked
in the section "Other Installers". Text from the distrib page:

   A small installation image: can be downloaded quickly and should be
   recorded onto a removable disk. To use this, you will need a machine
   with an Internet connection.


Page not linked on the download page
is www.catb.org/~esr/faqs/smart-questions.html  Introduction text from that
page:

   In the world of hackers, the kind of answers you get to your technical
   questions depends as much on the way you ask the questions as on the
   difficulty of developing the answer. This guide will teach you how
   to ask questions in a way more likely to get you a satisfactory answer.

 
> Regards,
> Glen

Groeten
Geert Stappers
-- 
Silence is hard to parse

Possible to force installing from the mirror instead of the installation media?

[Glen Huang]

Hi,

I remember reading it somewhere in a Debian doc (though I can no
longer find it) that only netboot automatically installs the base
system from a mirror, other media install from the media itself and
then upgrade via the mirror if allowed.

I wonder if it's possible to force the installer to use the mirror for
installing the base system? Currently, my installer installs two
versions of kernels, one from the media, the other from upgrading via
the mirror, which seems like a waste.

I couldn't find the preseed directive that controls this. Would be
grateful if someone could shed some light.

Regards,
Glen

Bug#668923: marked as done (debian-installer: Installing grub fails: /boot on raid1; / on lvm2 on dm-crypt on raid)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #668923,
regarding debian-installer: Installing grub fails: /boot on raid1; / on lvm2 on 
dm-crypt on raid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
668923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: testing
Severity: important

Dear Maintainer,

   * What led up to the situation?
I tried installing Debian using the partition layout provided in the 
gentoo wiki: 
http://en.gentoo-wiki.com/wiki/Root_filesystem_over_LVM2,_DM-Crypt_and_RAID
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I went through the steps of debian-installer, configured the partitions 
like described above.
This is the output of gdisk (its for /dev/sda , but /dev/sdb is the 
same)
GPT fdisk (gdisk) version 0.8.2

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 853F5A88-B593-4BFC-88BC-DC825FB9BD90
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)End (sector)  Size   Code  Name
   120484095   1024.0 KiB  EF02  
   24096  585727   284.0 MiB   FD00  
   3  585728  1953525134   931.2 GiB   FD00  

   * What was the outcome of this action?
Grub install failed with an fatal error ( http://pastebin.com/2akhkUCR )
I tried around a little bit and discovered that the boot partition 
wasn't mounted at /target/boot while all other partitions were mounted at there 
respective place in /target.
Instead there was just a folder /target/grub with all the files that 
should have been gone to the boot partition.
After moving that folder to /target/bootbak, creating /target/boot, 
mounting /dev/md0 (the boot partition) there, copying all files from bootbak to 
boot (which is probably unnecessary) debian-installers "Install Grub 
bootloader" worked :)
So probably debian-installer missed mounting /dev/md0 to /target/boot 
so grub install failed.
   * What outcome did you expect instead?
Grub should have been installed without problems / the boot partition 
should have been mounted at /target/boot automatically

This problem occured as well with debian stable (but in a vm) and I didn't 
check whether the missing boot partition was the root of the problem there as 
well.
In my "real-world" installation the error occured both, with the above 
described partition setup and one with msdos partitiontable. But same goes 
here, I didn't check whether the missing boot partitin caused the problem there 
as well.

Furthermore /dev/md0 /boot was missing in /fstab. Instead the usb stick I 
installed from was in there to mount to /mnt/usb1 (or another number, can't 
remember).



-- System Information:
Debian Release: wheezy/sid (<-- I'm using testing, dont know what the sid does 
there, reportbug created this section..)
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Hi,

similar to the installation-reports bugs, I'm closing the grub-installer 
reports 
below.

These are reports for Debian 4 / 6 / 7 / 9 where grub-installer fails (for 
various reasons).


There have been numerous changes/improvements on this topics in the past, and 
also because of the age of the reports we should consider these problems as 
being fixed (or it is even reported in the bugs that they are fixed).
They are most likely of no use anymore for recent releases.

If you know, that the issue you reported (and gets closed here) is still 
existing in recent installation images, please file a new report for that with 
up-to-date details!

Thank you for filing these bug reports, they have been very useful at the time 
they were filed!


https://bugs.debian

Bug#612420: marked as done (installation-reports: Grub install error when installing from USB (Debian Squeeze))

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #612420,
regarding installation-reports: Grub install error when installing from USB 
(Debian Squeeze)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
612420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: important

I used "unetbootin" for installing Debian from USB.

In the final step of the installation, Grub wants to use the USB I'm using to
install Debian. It doesn't let me to choose the hard disk until I remove the
usb from the laptop, then I can install Grub properly in the hard disk.



-- Package-specific info:

Boot method: usb
Image version: debian 6 Stable (32 bits) netinstall
Date: 

Machine: Toshiba NB200
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20091104-00:01"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux MPB 2.6.30-2-amd64 #1 SMP Fri Sep 25 22:16:56 UTC 2009 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) 
HD Audio Controller [8086:284b] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 4 [8086:2845] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 6 [8086:2849] (rev 03)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 03)
lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0121]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1

Re: Help with installing debian

[Andrew M.A. Cater]

On Thu, Sep 23, 2021 at 08:28:46PM +0530, Rohan J. Tilwani wrote:
> Hello there,
> I am facing a serious issues installing the "Bullseye" version of debian.
> Especially with Disks. I would be glad if you help me out. I am trying to
> install live+nonfree latest version of debian. Initially i get error that
> says SM bus busy. After I boot into live environment, I get another issue.
> I cant locate my secondary HDD on Lenovo slim 5.(i5 11th gen, Nvidia MX450,
> 8gigs RAM, 256gigs SSD+1TB HDD). Please help.
> Thank you.

Hello Rohan,

This might be better asked on debian-user which is the mailing list for 
user support.

A couple of straightfrorward questions:

Is this a first ever Debian install for you?

Do you have any other operating system on the laptop that you wish to 
retain?

Do you wnt the laptop to only run Debian?

I would suggest that you use the standard Debian installer (rather than a 
Live DVD) and also that you use the unofficial installer which does contain
the firmware found in non-free.

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-11.0.0-amd64-netinst.iso
 is the small
netinst image.

Hope this helps,

With every good wish,

Andrew Cater

Help with installing debian

[Rohan J. Tilwani]

Hello there,
I am facing a serious issues installing the "Bullseye" version of debian.
Especially with Disks. I would be glad if you help me out. I am trying to
install live+nonfree latest version of debian. Initially i get error that
says SM bus busy. After I boot into live environment, I get another issue.
I cant locate my secondary HDD on Lenovo slim 5.(i5 11th gen, Nvidia MX450,
8gigs RAM, 256gigs SSD+1TB HDD). Please help.
Thank you.

Processed: Re: Bug#992305: Only one nic works at a time when installing Debian 11 and Gui (gnome)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 installation-reports
Bug #992305 [network-manager] Only one nic works at a time when installing 
Debian 11 and Gui (gnome)
Bug reassigned from package 'network-manager' to 'installation-reports'.
Ignoring request to alter found versions of bug #992305 to the same values 
previously set
Ignoring request to alter fixed versions of bug #992305 to the same values 
previously set

-- 
992305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#992305: Only one nic works at a time when installing Debian 11 and Gui (gnome)

[Andrei POPESCU]

Control: reassign -1 installation-reports

On Lu, 16 aug 21, 17:56:44, joebeasley...@gmail.com wrote:
> Package: 
> Version: <11>
> 
> Fresh Gui install. Two nics on different networks. If I enable one with
> network manager in gnome, it disables the other one. Re-enable the one
> it disabled, and it disables the other one??
> Turns out this was a graphical install that created file called
> ens3.nmconnection in /etc/NetworkManager/system-connections. I removed
> this file and rebooted. Both nics can now be enabled at the same time.
> A Text install creates a file called "Wired Connection 1" in the same
> folder. Removed it to resolve.
> Looks like these files get created if you install a graphical desktop
> (gnome) during the install.  Three different installs, same results. 
> I did a text install with no gui, then installed the gnome desktop
> after reboot. No issues.
> 
> This is a virtual machine install running on an Ubuntu 18.04.1. Kernel
> 5.4.0-77-generic #86~18.04.2-Ubuntu SMP.  64 Gigs Ram.  
> qemu-kvm version 1:2.11_dfsg-1ubuntu7.37
> 
> Debian ISO debian-11.0.0-amd64-netinst.iso   
> size  395.3 MB
> md5sum  499953266841cae41612310e65659456
> sha256sum ae6d563d2444665316901fe7091059ac34b8f67ba30f9159f7cef7d2fdc5b
> f8a
> 
> 
> Installs:
> Debian Gnu/linux 11 (bullseye) x86_64
> kernel 5.10.0-8-amd64
> shell: bash 5.1.4

Reassigning to correct (pseudo-)package.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Bug#825916: marked as done (installation-reports: Installing Debian with AMD/ATI Radeon graphics card does not go well)

[Debian Bug Tracking System]

Your message dated Sun, 29 Aug 2021 21:09:59 +0200
with message-id <20210829210959.f3d5b403cce267ff9e69d...@mailbox.org>
and subject line Closing bugreports related to missing/not installed firmware
has caused the Debian Bug report #825916,
regarding installation-reports: Installing Debian with AMD/ATI Radeon graphics 
card does not go well
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: important

When i install Debian on computer with AMD/ATI Radeon graphics card it does no
go well.

After installation there is problem booting into the graphical desktop (GNOME)
because it needs firmware-linux-nonfree and other packages to it seems.

This is a big problem for a new user that wants to try Debian for the first
time and have no idea why the system cant start the graphical desktop and what
commands to type.

I would at least expect to be able to start the desktop into some low
resolution mode like in Windows where you can get into the desktop even though
you dont have the correct driver.

Then maybe the user is able to find information on the web/IRC to fix the
problem.



-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=da_DK.utf8, LC_CTYPE=da_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi,

since we have some kind of a next-generation installer, when it comes to
installation of (non-free) firmware, I'm closing all related old bugreports.

They have been helpful at the time, when they were filed, however now we have
a completely new situation / mechanism in place for this, so let's make a cut
now and close such bugs, and let people file new ones with recent installer
versions, if they still experience problems.


Thanks to all reporters!

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#990892: debian-installer: Please add an option for installing Nvidia proprietary video driver

[Georgi Naplatanov]

Package: debian-installer
Version: Debian 11
Severity: wishlist

Dear Maintainer,

please add an option for installing proprietary Nvidia video driver during 
installation.

Kind regards
Georgi

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Re: Failure installing Debian Buster from netboot.tar.gz. Kernel not matching repository.

[Geert Stappers]

On Sat, Jun 05, 2021 at 06:57:32PM +0200, Guido Ackermann wrote:
> Hello,
> 
>  ...  please tell me how to fix this error to my
> netboot-infrastructure

What about fetching the netboot.tar.gz from the very same
repository as the repository used further in the install process?


> 
> regards
>   Guido Ackermann
>   Netzwerk & Systemspezialist
>   VRG-Grupppe
> 
> Schlage nie jemanden mit einer Brille.
> Nimm lieber einen Knüppel.



Regards
Geert Stappers
-- 
Silence is hard to parse

Failure installing Debian Buster from netboot.tar.gz. Kernel not matching repository.

[Guido Ackermann]

Hello,
there is, again and not only once again, a failure in debian bullseye 
netboot image. on last friday there was a failure acording to keys not 
yet active. "try again in 1d ...". This reminds me strongly to a add in
german TV for some kind of sexual stimulanz. Same for buster, but there
only for the security-repository which the installer claimed unusable
until further investigation. What bothers me most is the fact that the
installer blames me for having a networkproblem. Also stating that i
should use the repository deb.debian.org, which i was actual using.
This is not the quality of debian"we are ready when things are ready"
distribution i would expect. An not nearly the quality it was ten years
ago. 
Even worse. After waiting for one Day, hey it's weekend why not wait a
bit,  i tried to install again. Tried. Because nothing works. This time
because the netboot-kernel had a version not found in repository. So no
kernelmodules could be found and the installer stops working. This was
not the first time. But i hope it will be the last time. If you need hlt
in testing the netboot of different netinstallimages i could make an
automated testsuite which will install minimal debian to a vm and mail
you if something is wrong. 

In the meantime, please tell me how to fix this error to my
netboot-infrastructure as i do not have the time to investigate this
more deeply. 

regards
Guido Ackermann
Netzwerk & Systemspezialist
VRG-Grupppe
-- 
Schlage nie jemanden mit einer Brille.
Nimm lieber einen Knüppel.


signature.asc
Description: PGP signature

Installing Debian from HDD with Win7 to USB stick

[Cmdte Alpha Tigre Z]

Dear developers and mantainers,

I want to install Debian to a USB stick from a hard drive
with Windows 7.

This is what I have already done:

I put an ISO DVD image of Debian 10.8 at C:\
I put vmlinuz and initrd.gz from hd-media at C:\tmpx\
I extracted g2ldr and g2ldr.mbr from the ISO image and put it at C:\tmpx\
I extracted setup.exe and win32-loader.ini from the ISO image and put it at C:\
I modified the win32-loader.ini (without the leading spaces) from:
[installer]
kernel=linux
arch=i386
i386/linux=install.386/vmlinuz
i386/initrd=install.386/initrd.gz
i386/gtk/linux=install.386/vmlinuz
i386/gtk/initrd=install.386/gtk/initrd.gz

[grub]
g2ldr=g2ldr
g2ldr.mbr=g2ldr.mbr
to:
[installer]
kernel=linux
arch=i386
i386/linux=tmpx/vmlinuz
i386/initrd=tmpx/initrd.gz

[grub]
g2ldr=tmpx/g2ldr
g2ldr.mbr=tmpx/g2ldr.mbr
Note: g2ldr and g2ldr.mbr can not be at root, otherwise
preinstallation fails when trying to copy them there.

I ran setup.exe and went to the end of the procedure successfully.

However, I saw that win32-loader (setup.exe) modified the initrd.gz
from hd-media.
As I understood from the log of win32-loader, some "preseed" information
was added to initrd.gz.  I saw it with 7-Zip and found that the data
"inside" the
initrd that is inside initrd.gz was unmodified.  Since 7-Zip reported that the
compressed initrd was modified and it also gave a wrong compressed size,
I opened initrd.gz with an hexadecimal editor and saw that some data was
"appended to" but not "put into" initrd.gz

Perhaps it is normal behaviour for the initrd.gz from the ISO, but
since I'm using
the one from hd-media on Debian's mirrors, I want to be sure that
nothing bad happened
and that I can continue with the installation.

Thanks in advance for your time and help.

Sincerely,
Santiago Pinto.

Re: Bug#954134: [d-i bullseye alpha2] installing grub fails

[Holger Wansing]

Hi,

Holger Wansing  wrote (Sun, 28 Mar 2021 14:39:41 +0200):
> Hi,
> 
> Steve McIntyre  wrote (Sat, 21 Mar 2020 17:00:59 +):
> >Hmm, this is getting annoying:
> >while doing several test installs, I thought I had a path how to reproduce
> >the issue, but then suddenly it looked completely different than before.
> >So, that's something between "some portion of coincidence involved" and
> >"wow, not it looks like a hardware failure".
> >
> >And since I was never able to reproduce the issue on amd64, it seems at
> >least to be a i386-only issue, and thus could be considered as a corner 
> >case...

Since I cannot reproduce this for a long time now, I'm closing this report.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 13/02/2021 23:08, Steve McIntyre wrote:

On Sat, Feb 13, 2021 at 10:38:03PM +, Bernard McNeill wrote:

Bernard McNeill  wrote (Sat, 13 Feb 2021 19:45:27 +):

The installation appears to go fine.
The installer creates a new entry 'Debian' in the boot list.
Machine rebooted, pressing F12 to get into one-time boot option.
Choice is 'Debian', or 'Windows Boot Manager'.
Take option 'Debian' and system then hangs with:
'Press F1 key to retry boot.'
'Press F2 key to reboot into setup.'
'Press F5 key to run onboard diagnostics.'


During Debian installation, rather at the end, you have been prompted
where to install the GRUB bootloader, right?
What did you choose there?

Is the Windows system still bootable as usual?

Providing the installer logfiles would also be good, by the way...
See 
https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s03.html#save-logs


Holger



+ During Debian installation, rather at the end, you have been prompted
+ where to install the GRUB bootloader, right?
I do not think I was given any choice - everything ran through to the point
where I was warned to remove the installation media before rebooting.


It's a UEFI system, so that's normal. I think what you're hitting here
looks like a similar bug to https://bugs.debian.org/905319. If you
follow the same workaround as suggested in

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905319#10

If you use the installation media to boot into rescue mode, it also
has an option to do the EFI removable media path thing.

***Be aware***: this will stop your system booting Windows directly,
you'll have to go via Grub to get there. I think there is a firmware
bug that's the root cause of your problem.


I have just realised something else:

As above, if 'Debian' boot option taken, system hangs.
Cold restart with external HDD (containing Debian) still plugged in, no 
F12'ing (to select boot option) results in booting into Windows.


This is a surprise to me, because 'Debian' is the first option in the 
boot order list. With this order, surely system should have hung?


Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 13/02/2021 23:08, Steve McIntyre wrote:

On Sat, Feb 13, 2021 at 10:38:03PM +, Bernard McNeill wrote:

Bernard McNeill  wrote (Sat, 13 Feb 2021 19:45:27 +):

The installation appears to go fine.
The installer creates a new entry 'Debian' in the boot list.
Machine rebooted, pressing F12 to get into one-time boot option.
Choice is 'Debian', or 'Windows Boot Manager'.
Take option 'Debian' and system then hangs with:
'Press F1 key to retry boot.'
'Press F2 key to reboot into setup.'
'Press F5 key to run onboard diagnostics.'


During Debian installation, rather at the end, you have been prompted
where to install the GRUB bootloader, right?
What did you choose there?

Is the Windows system still bootable as usual?

Providing the installer logfiles would also be good, by the way...
See 
https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s03.html#save-logs


Holger



+ During Debian installation, rather at the end, you have been prompted
+ where to install the GRUB bootloader, right?
I do not think I was given any choice - everything ran through to the point
where I was warned to remove the installation media before rebooting.


It's a UEFI system, so that's normal. I think what you're hitting here
looks like a similar bug to https://bugs.debian.org/905319. If you
follow the same workaround as suggested in

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905319#10

If you use the installation media to boot into rescue mode, it also
has an option to do the EFI removable media path thing.

***Be aware***: this will stop your system booting Windows directly,
you'll have to go via Grub to get there. I think there is a firmware
bug that's the root cause of your problem.



Question-1:
Is it possible to create a bootable flash drive, such that:

If the bootable flash drive is plugged in, and the machine rebooted with 
F12 to get into one-time boot, then booted from that flash drive, then 
control passes to the Debian installation on the external HDD.


If the bootable flash drive is not plugged in, control just passes to 
Windows.


Question-2:
If it is believed that there is a firmware bug, has this been reported 
to the manufacturer/supplier?


Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Steve McIntyre]

On Sat, Feb 13, 2021 at 10:38:03PM +, Bernard McNeill wrote:
>> Bernard McNeill  wrote (Sat, 13 Feb 2021 19:45:27 
>> +):
>> > The installation appears to go fine.
>> > The installer creates a new entry 'Debian' in the boot list.
>> > Machine rebooted, pressing F12 to get into one-time boot option.
>> > Choice is 'Debian', or 'Windows Boot Manager'.
>> > Take option 'Debian' and system then hangs with:
>> > 'Press F1 key to retry boot.'
>> > 'Press F2 key to reboot into setup.'
>> > 'Press F5 key to run onboard diagnostics.'
>> 
>> During Debian installation, rather at the end, you have been prompted
>> where to install the GRUB bootloader, right?
>> What did you choose there?
>> 
>> Is the Windows system still bootable as usual?
>> 
>> Providing the installer logfiles would also be good, by the way...
>> See 
>> https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s03.html#save-logs
>> 
>> 
>> Holger
>> 
>> 
>+ During Debian installation, rather at the end, you have been prompted
>+ where to install the GRUB bootloader, right?
>I do not think I was given any choice - everything ran through to the point
>where I was warned to remove the installation media before rebooting.

It's a UEFI system, so that's normal. I think what you're hitting here
looks like a similar bug to https://bugs.debian.org/905319. If you
follow the same workaround as suggested in

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905319#10

If you use the installation media to boot into rescue mode, it also
has an option to do the EFI removable media path thing.

***Be aware***: this will stop your system booting Windows directly,
you'll have to go via Grub to get there. I think there is a firmware
bug that's the root cause of your problem.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 13/02/2021 21:43, Holger Wansing wrote:

Hi,

Bernard McNeill  wrote (Sat, 13 Feb 2021 19:45:27 +):

The installation appears to go fine.
The installer creates a new entry 'Debian' in the boot list.
Machine rebooted, pressing F12 to get into one-time boot option.
Choice is 'Debian', or 'Windows Boot Manager'.
Take option 'Debian' and system then hangs with:
'Press F1 key to retry boot.'
'Press F2 key to reboot into setup.'
'Press F5 key to run onboard diagnostics.'


During Debian installation, rather at the end, you have been prompted
where to install the GRUB bootloader, right?
What did you choose there?

Is the Windows system still bootable as usual?


Providing the installer logfiles would also be good, by the way...
See 
https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s03.html#save-logs


Holger



+ During Debian installation, rather at the end, you have been prompted
+ where to install the GRUB bootloader, right?
I do not think I was given any choice - everything ran through to the 
point where I was warned to remove the installation media before rebooting.


+ Is the Windows system still bootable as usual?
Yes.

+ Providing the installer logfiles would also be good, by the way...
+ See 
https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s03.html#save-logs

On a quick look, I don't see how to get at these if I can't get into Debian.

Best regards






I don't think I was prompted

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Holger Wansing]

Hi,

Bernard McNeill  wrote (Sat, 13 Feb 2021 19:45:27 +):
> The installation appears to go fine.
> The installer creates a new entry 'Debian' in the boot list.
> Machine rebooted, pressing F12 to get into one-time boot option.
> Choice is 'Debian', or 'Windows Boot Manager'.
> Take option 'Debian' and system then hangs with:
> 'Press F1 key to retry boot.'
> 'Press F2 key to reboot into setup.'
> 'Press F5 key to run onboard diagnostics.'

During Debian installation, rather at the end, you have been prompted
where to install the GRUB bootloader, right?
What did you choose there?

Is the Windows system still bootable as usual?


Providing the installer logfiles would also be good, by the way...
See 
https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s03.html#save-logs


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 13/02/2021 19:08, Holger Wansing wrote:

Hi,

Bernard McNeill  wrote (Sat, 13 Feb 2021 18:24:35 +):

And there was a difference: This time, when the partitioner came up, it
could see the internal SSD (previously it didn't, just showed the
external HDD and the installer flash drive).

I have no idea why this should be, but carried on installing Debian over
the entire external HDD.

And I still get the same result...it's as though the installer is not
setting the Debian boot option to point to the HDD.


What's the error/problem/message in detail?
Installation wents through fine, but machine cannot boot newly installed
Debian system?
Or installation fails at some step?


Holger



The installation appears to go fine.
The installer creates a new entry 'Debian' in the boot list.
Machine rebooted, pressing F12 to get into one-time boot option.
Choice is 'Debian', or 'Windows Boot Manager'.
Take option 'Debian' and system then hangs with:
'Press F1 key to retry boot.'
'Press F2 key to reboot into setup.'
'Press F5 key to run onboard diagnostics.'

None of which lead to Debian.

Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Holger Wansing]

Hi,

Bernard McNeill  wrote (Sat, 13 Feb 2021 18:24:35 +):
> And there was a difference: This time, when the partitioner came up, it 
> could see the internal SSD (previously it didn't, just showed the 
> external HDD and the installer flash drive).
> 
> I have no idea why this should be, but carried on installing Debian over 
> the entire external HDD.
> 
> And I still get the same result...it's as though the installer is not 
> setting the Debian boot option to point to the HDD.

What's the error/problem/message in detail?
Installation wents through fine, but machine cannot boot newly installed
Debian system?
Or installation fails at some step?


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 10/02/2021 10:11, Bernard McNeill wrote:



On 08/02/2021 23:06, Lou Poppler wrote:

On Mon, 2021-02-08 at 22:59 +, Bernard McNeill wrote:


On 08/02/2021 22:44, Lou Poppler wrote:

On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote:
[...]

I have one SSD (which has Win-10 on it), there is no other disk
(spinning or otherwise) on the machine.
The BIOS System Information says 'M.2. SATA =(none)'
and 'M.2. PCIe SSD-0=87NB51ASK5HS'.
However: Under BIOS System Configuration, 'SATA Operation' is set to
'RAID On', [other options are 'Disabled' and 'AHCI' ].



Interesting that Dell is making a distinction here between SATA and 
PCIe mass

storage, but calling its RAID foolishness "SATA Operation - RAID On".
Does this imply maybe that the SSD connected via PCIe and not via 
the SATA

wiring/controller, is exempt from the RAID interference?  I don't know.

It sure would be nice if that is what they mean though.
Maybe you can carefully test how this really works.
(Make the backup first though)




Is it even possible to RAID an SDD?


With software RAID, you can combine all manner of storage devices into a
"managed device" even different physical types of storage.  What this 
built-in
factory RAID might be is unclear to me.  From the misbehavior of the 
system
regarding your sometimes attached external USB disk (with the 
attempted debian

install on it) it seems likely that the factory/BIOS RAID thing might be
interposing itself between disks as seen by running programs (like the 
debian

installer) and the actual hardware storage itself.

[...]



FWIW, I found this link relating to Dell SSD, SATA and AHCI/RAID On.

https://www.dell.com/community/Laptops-General-Read-Only/Dell-M-2-FAQ-regarding-AHCI-vs-RAID-ON-Storage-Drivers-M-2-Lanes/td-p/507257 

But still unclear to me if changing 'RAID On' to 'AHCI' is going to 
cause a problem.


Best regards


FYI
Being persistent, I arranged for backup Windows knowledge in case 
everything fell apart, entered Windows safe mode, rebooted and changed 
the BIOS to: SATA Operation=AHCI (from RAID On), rebooted and got out of 
Windows safe mode.


Windows seemed undamaged, so I went on to reinstall Debian on the 
external HDD.


And there was a difference: This time, when the partitioner came up, it 
could see the internal SSD (previously it didn't, just showed the 
external HDD and the installer flash drive).


I have no idea why this should be, but carried on installing Debian over 
the entire external HDD.


And I still get the same result...it's as though the installer is not 
setting the Debian boot option to point to the HDD.


Any ideas gratefully received.

Re: Installing firmware and ISO images on CD/DVD

[Jeffrey Walton]

On Tue, Feb 9, 2021 at 7:28 AM John Paul Adrian Glaubitz
 wrote:
>
> > On Feb 9, 2021, at 1:22 PM, Jeffrey Walton  wrote:
> >
> > Hi Everyone,
> >
> > I'd like to install the additional firmware required for PowerPC. It
> > is briefly discussed at
> > https://www.debian.org/releases/jessie/amd64/ch06s04.html.en.
> >
> > The problem I am having is, PowerMac's don't have an eject button. I
> > can't eject the installer to add the firmware CD from
> > http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/8.10.0+nonfree/powerpc/iso-cd/.
> > I tried to use a USB stick but the firmware was not found. (I don't
> > even think the USB bus was scanned - the led on the usb stick did not
> > blink).
>
> You can eject the CD from the command line with:
>
> # eject /dev/cdrom
>
> or
>
> # eject /dev/sr0
>
> > I think the installer should be modified in two places to support an
> > eject operation. The first place is the "Missing firmware" screen. The
> > second place is the "Configure Apt" screen.
>
> That could potentially be done but we‘re adding firmware on the ISOs in the 
> near future anyway.

That's probably a good choice.

The open source purist can decline to use proprietary firmware. Others
can choose to accept the proprietary software, if desired.

Jeff

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 08/02/2021 23:06, Lou Poppler wrote:

On Mon, 2021-02-08 at 22:59 +, Bernard McNeill wrote:


On 08/02/2021 22:44, Lou Poppler wrote:

On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote:
[...]

I have one SSD (which has Win-10 on it), there is no other disk
(spinning or otherwise) on the machine.
The BIOS System Information says 'M.2. SATA =(none)'
and 'M.2. PCIe SSD-0=87NB51ASK5HS'.
However: Under BIOS System Configuration, 'SATA Operation' is set to
'RAID On', [other options are 'Disabled' and 'AHCI' ].



Interesting that Dell is making a distinction here between SATA and PCIe mass
storage, but calling its RAID foolishness "SATA Operation - RAID On".
Does this imply maybe that the SSD connected via PCIe and not via the SATA
wiring/controller, is exempt from the RAID interference?  I don't know.

It sure would be nice if that is what they mean though.
Maybe you can carefully test how this really works.
(Make the backup first though)




Is it even possible to RAID an SDD?


With software RAID, you can combine all manner of storage devices into a
"managed device" even different physical types of storage.  What this built-in
factory RAID might be is unclear to me.  From the misbehavior of the system
regarding your sometimes attached external USB disk (with the attempted debian
install on it) it seems likely that the factory/BIOS RAID thing might be
interposing itself between disks as seen by running programs (like the debian
installer) and the actual hardware storage itself.

[...]



FWIW, I found this link relating to Dell SSD, SATA and AHCI/RAID On.

https://www.dell.com/community/Laptops-General-Read-Only/Dell-M-2-FAQ-regarding-AHCI-vs-RAID-ON-Storage-Drivers-M-2-Lanes/td-p/507257
But still unclear to me if changing 'RAID On' to 'AHCI' is going to 
cause a problem.


Best regards

Re: Installing firmware and ISO images on CD/DVD

[Lou Poppler]

On Tue, 2021-02-09 at 07:22 -0500, Jeffrey Walton wrote:
> Hi Everyone,
> 
> I'd like to install the additional firmware required for PowerPC. It
> is briefly discussed at
> https://www.debian.org/releases/jessie/amd64/ch06s04.html.en.
> 
> The problem I am having is, PowerMac's don't have an eject button. I
> can't eject the installer to add the firmware CD from
> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/8.10.0+nonfree/powerpc/iso-cd/.
> I tried to use a USB stick but the firmware was not found. (I don't
> even think the USB bus was scanned - the led on the usb stick did not
> blink).
> 
> I think the installer should be modified in two places to support an
> eject operation. The first place is the "Missing firmware" screen. The
> second place is the "Configure Apt" screen.
> 
> Jeff
> 
The second CD you reference [8.10.0+nonfree] is both an installer and a source
of firmware files.  You should be able to install without ejecting, I think?

Re: Installing firmware and ISO images on CD/DVD

[John Paul Adrian Glaubitz]

Hello!

> On Feb 9, 2021, at 1:22 PM, Jeffrey Walton  wrote:
> 
> Hi Everyone,
> 
> I'd like to install the additional firmware required for PowerPC. It
> is briefly discussed at
> https://www.debian.org/releases/jessie/amd64/ch06s04.html.en.
> 
> The problem I am having is, PowerMac's don't have an eject button. I
> can't eject the installer to add the firmware CD from
> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/8.10.0+nonfree/powerpc/iso-cd/.
> I tried to use a USB stick but the firmware was not found. (I don't
> even think the USB bus was scanned - the led on the usb stick did not
> blink).

You can eject the CD from the command line with:

# eject /dev/cdrom

or

# eject /dev/sr0

> I think the installer should be modified in two places to support an
> eject operation. The first place is the "Missing firmware" screen. The
> second place is the "Configure Apt" screen.

That could potentially be done but we‘re adding firmware on the ISOs in the 
near future anyway.

Adrian

Installing firmware and ISO images on CD/DVD

[Jeffrey Walton]

Hi Everyone,

I'd like to install the additional firmware required for PowerPC. It
is briefly discussed at
https://www.debian.org/releases/jessie/amd64/ch06s04.html.en.

The problem I am having is, PowerMac's don't have an eject button. I
can't eject the installer to add the firmware CD from
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/8.10.0+nonfree/powerpc/iso-cd/.
I tried to use a USB stick but the firmware was not found. (I don't
even think the USB bus was scanned - the led on the usb stick did not
blink).

I think the installer should be modified in two places to support an
eject operation. The first place is the "Missing firmware" screen. The
second place is the "Configure Apt" screen.

Jeff

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 09/02/2021 00:43, Lou Poppler wrote:

On Mon, 2021-02-08 at 22:59 +, Bernard McNeill wrote:


But, as I think I mentioned earlier, I am very reluctant indeed to mess
around with Windows itself.
I have backed up the user data, but I am not at all sure how to
re-install Windows itself.  If the machine failed I suspect I would take
it to a specialist with a copy of the user data.


I suggest at this point you should try out one of the debian "live" images.
These can be copied to a USB stick (via win32diskimager or others) just like you
copied the installer to USB.  Then, you boot into the live image and it runs
completely from the USB stick -- you have a mostly complete linux system you can
experiment with, without permanently writing it onto any other disks, and
without the live system needing to write to any other disks.

I would suggest the current stable "gnome" live system, which is familiar to
Windows users -- and I also suggest the so-called "non-free" version (which just
means it includes various firmware files for wifi or fancy graphics adapters,
etc.)

Download here:
https://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/current-live/amd64/iso-hybrid/debian-live-10.8.0-amd64-gnome+nonfree.iso



I am going to try your suggestion.

For the record, I did fully reinstall Debian with Fastboot (both Windows 
and BIOS) disabled.  I got the same issues as before, but can confirm 
(because I was looking for it) that the installer/partitioner does not 
seem to see the SSD.

It could see both the install USB flash drive and the external USB HDD.

Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 22:59 +, Bernard McNeill wrote:
> 
> But, as I think I mentioned earlier, I am very reluctant indeed to mess 
> around with Windows itself.
> I have backed up the user data, but I am not at all sure how to 
> re-install Windows itself.  If the machine failed I suspect I would take 
> it to a specialist with a copy of the user data.

I suggest at this point you should try out one of the debian "live" images.
These can be copied to a USB stick (via win32diskimager or others) just like you
copied the installer to USB.  Then, you boot into the live image and it runs
completely from the USB stick -- you have a mostly complete linux system you can
experiment with, without permanently writing it onto any other disks, and
without the live system needing to write to any other disks.

I would suggest the current stable "gnome" live system, which is familiar to
Windows users -- and I also suggest the so-called "non-free" version (which just
means it includes various firmware files for wifi or fancy graphics adapters,
etc.)

Download here: 
https://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/current-live/amd64/iso-hybrid/debian-live-10.8.0-amd64-gnome+nonfree.iso

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 22:59 +, Bernard McNeill wrote:
> 
> On 08/02/2021 22:44, Lou Poppler wrote:
> > On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote:
> > [...]
> > > I have one SSD (which has Win-10 on it), there is no other disk
> > > (spinning or otherwise) on the machine.
> > > The BIOS System Information says 'M.2. SATA =(none)'
> > > and 'M.2. PCIe SSD-0=87NB51ASK5HS'.
> > > However: Under BIOS System Configuration, 'SATA Operation' is set to
> > > 'RAID On', [other options are 'Disabled' and 'AHCI' ].
> > > 
> > 
> > Interesting that Dell is making a distinction here between SATA and PCIe 
> > mass
> > storage, but calling its RAID foolishness "SATA Operation - RAID On".
> > Does this imply maybe that the SSD connected via PCIe and not via the SATA
> > wiring/controller, is exempt from the RAID interference?  I don't know.
> > 
> > It sure would be nice if that is what they mean though.
> > Maybe you can carefully test how this really works.
> > (Make the backup first though)
> > 
> > 
> 
> Is it even possible to RAID an SDD?
> 
With software RAID, you can combine all manner of storage devices into a
"managed device" even different physical types of storage.  What this built-in
factory RAID might be is unclear to me.  From the misbehavior of the system
regarding your sometimes attached external USB disk (with the attempted debian
install on it) it seems likely that the factory/BIOS RAID thing might be
interposing itself between disks as seen by running programs (like the debian
installer) and the actual hardware storage itself.

> But, as I think I mentioned earlier, I am very reluctant indeed to mess 
> around with Windows itself.
> I have backed up the user data, but I am not at all sure how to 
> re-install Windows itself.  If the machine failed I suspect I would take 
> it to a specialist with a copy of the user data.

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 08/02/2021 22:44, Lou Poppler wrote:

On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote:
[...]

I have one SSD (which has Win-10 on it), there is no other disk
(spinning or otherwise) on the machine.
The BIOS System Information says 'M.2. SATA =(none)'
and 'M.2. PCIe SSD-0=87NB51ASK5HS'.
However: Under BIOS System Configuration, 'SATA Operation' is set to
'RAID On', [other options are 'Disabled' and 'AHCI' ].


Interesting that Dell is making a distinction here between SATA and PCIe mass
storage, but calling its RAID foolishness "SATA Operation - RAID On".
Does this imply maybe that the SSD connected via PCIe and not via the SATA
wiring/controller, is exempt from the RAID interference?  I don't know.

It sure would be nice if that is what they mean though.
Maybe you can carefully test how this really works.
(Make the backup first though)



Is it even possible to RAID an SDD?

But, as I think I mentioned earlier, I am very reluctant indeed to mess 
around with Windows itself.
I have backed up the user data, but I am not at all sure how to 
re-install Windows itself.  If the machine failed I suspect I would take 
it to a specialist with a copy of the user data.


Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote:
[...]
> I have one SSD (which has Win-10 on it), there is no other disk 
> (spinning or otherwise) on the machine.
> The BIOS System Information says 'M.2. SATA =(none)'
> and 'M.2. PCIe SSD-0=87NB51ASK5HS'.
> However: Under BIOS System Configuration, 'SATA Operation' is set to 
> 'RAID On', [other options are 'Disabled' and 'AHCI' ].
> 
Interesting that Dell is making a distinction here between SATA and PCIe mass
storage, but calling its RAID foolishness "SATA Operation - RAID On".
Does this imply maybe that the SSD connected via PCIe and not via the SATA
wiring/controller, is exempt from the RAID interference?  I don't know.

It sure would be nice if that is what they mean though.  
Maybe you can carefully test how this really works.
(Make the backup first though)

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote:
> 
> On 08/02/2021 21:57, Lou Poppler wrote:
> > On Mon, 2021-02-08 at 20:47 +, Bernard McNeill wrote:
> > > 
> > > On 08/02/2021 20:33, Cyril Brulebois wrote:
> > > > Bernard McNeill  (2021-02-08):
> > > > > It says to 'Change the SATA from RAID On to AHCI, without this change 
> > > > > Linux
> > > > > will not find SSD'.
> > > > > Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my
> > > > > copy of this model - so not relevant ?
> > > > 
> > > > Used for almost anything really, HDD, SSD, USB sticks, etc.
> > > > 
> > > > > In passing, I note the same link shows a need to disable Secure Boot -
> > > > > is this now obsolete?
> > > > 
> > > > Likely. We've started supporting SB with Debian 10 (buster).
> > > > 
> > > > 
> > > > Cheers,
> > > > 
> > > 
> > > If I change the SATA from RAID On to AHCI, do I mess up whatever is
> > > currently on the SSD?
> > > 
> > > Best regards
> > > 
> > 
> > See 
> > https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984
> > 
> > You have Windows on a regular, spinning hard disk in the machine, and you 
> > also have an
> > unused SSD -- is this correct?  Or maybe they are already RAIDed together 
> > by the factory?
> > 
> > I thing especially if you are now introducing a third external disk to the 
> > mix, you probably
> > do not want this factory RAID thing, but I don't know how safe it is to 
> > turn it off if you
> > already have two mass-storage devices controlled by the thing.
> > 
> 
> + You have Windows on a regular, spinning hard disk in the machine, and 
> + you also have an
> + unused SSD -- is this correct?  Or maybe they are already RAIDed
> + together by the factory?
> I have one SSD (which has Win-10 on it), there is no other disk 
> (spinning or otherwise) on the machine.
> The BIOS System Information says 'M.2. SATA =(none)'
> and 'M.2. PCIe SSD-0=87NB51ASK5HS'.
> However: Under BIOS System Configuration, 'SATA Operation' is set to 
> 'RAID On', [other options are 'Disabled' and 'AHCI' ].
> 
> Best regards

That Dell Community webpage also says there is a *chance* that you can change
the BIOS option, and get into Windows "safe mode" and recover.  
I strongly suggest making a backup now, of anything in the windows install that
you do not want to lose.

[ also note, I made a couple small modernizing edits to 
https://wiki.debian.org/InstallingDebianOn/Dell/Dell_XPS_13_9360  ]

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 08/02/2021 22:08, Lou Poppler wrote:

On Mon, 2021-02-08 at 14:57 -0700, Lou Poppler wrote:


See 
https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984


Reading more on that page looks like you should not change the setting unless
you are prepared to re-install your Windows; but also looks like you cannot
install linux beside your Windows unless you _DO_ change the setting.
Can you backup and then restore your existing windows setup?

I have saved the Win-10 user data, but regard destroying and recreating 
Windows as something only to be attempted in the event of a machine 
failure, not simply my wish to experiment with Linux.
That's why I bought an external HDD - idea was Linux goes on that, not 
touching Win-10 or the Win-10 user data on the SDD.


Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 08/02/2021 21:57, Lou Poppler wrote:

On Mon, 2021-02-08 at 20:47 +, Bernard McNeill wrote:


On 08/02/2021 20:33, Cyril Brulebois wrote:

Bernard McNeill  (2021-02-08):

It says to 'Change the SATA from RAID On to AHCI, without this change Linux
will not find SSD'.
Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my
copy of this model - so not relevant ?


Used for almost anything really, HDD, SSD, USB sticks, etc.


In passing, I note the same link shows a need to disable Secure Boot -
is this now obsolete?


Likely. We've started supporting SB with Debian 10 (buster).


Cheers,



If I change the SATA from RAID On to AHCI, do I mess up whatever is
currently on the SSD?

Best regards


See 
https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984

You have Windows on a regular, spinning hard disk in the machine, and you also 
have an
unused SSD -- is this correct?  Or maybe they are already RAIDed together by 
the factory?

I thing especially if you are now introducing a third external disk to the mix, 
you probably
do not want this factory RAID thing, but I don't know how safe it is to turn it 
off if you
already have two mass-storage devices controlled by the thing.

+ You have Windows on a regular, spinning hard disk in the machine, and 
+ you also have an

+ unused SSD -- is this correct?  Or maybe they are already RAIDed
+ together by the factory?
I have one SSD (which has Win-10 on it), there is no other disk 
(spinning or otherwise) on the machine.

The BIOS System Information says 'M.2. SATA =(none)'
and 'M.2. PCIe SSD-0=87NB51ASK5HS'.
However: Under BIOS System Configuration, 'SATA Operation' is set to 
'RAID On', [other options are 'Disabled' and 'AHCI' ].


Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 14:57 -0700, Lou Poppler wrote:
> 
> See 
> https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984
> 
Reading more on that page looks like you should not change the setting unless
you are prepared to re-install your Windows; but also looks like you cannot
install linux beside your Windows unless you _DO_ change the setting.  
Can you backup and then restore your existing windows setup?

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 20:47 +, Bernard McNeill wrote:
> 
> On 08/02/2021 20:33, Cyril Brulebois wrote:
> > Bernard McNeill  (2021-02-08):
> > > It says to 'Change the SATA from RAID On to AHCI, without this change 
> > > Linux
> > > will not find SSD'.
> > > Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my
> > >copy of this model - so not relevant ?
> > 
> > Used for almost anything really, HDD, SSD, USB sticks, etc.
> > 
> > > In passing, I note the same link shows a need to disable Secure Boot -
> > > is this now obsolete?
> > 
> > Likely. We've started supporting SB with Debian 10 (buster).
> > 
> > 
> > Cheers,
> > 
> 
> If I change the SATA from RAID On to AHCI, do I mess up whatever is 
> currently on the SSD?
> 
> Best regards
> 
See 
https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984

You have Windows on a regular, spinning hard disk in the machine, and you also 
have an
unused SSD -- is this correct?  Or maybe they are already RAIDed together by 
the factory?

I thing especially if you are now introducing a third external disk to the mix, 
you probably
do not want this factory RAID thing, but I don't know how safe it is to turn it 
off if you
already have two mass-storage devices controlled by the thing.

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 20:07 +, Bernard McNeill wrote:
[...]
> I was planning the re-install, and came across this page:
> https://wiki.debian.org/InstallingDebianOn/Dell/Dell_XPS_13_9360
> 
> It says to 'Change the SATA from RAID On to AHCI, without this change 
> Linux will not find SSD'.
> Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my 
> copy of this model - so not relevant ?
> 2. I don't care if Linux just 'finds' the SSD.
>But I care very greatly about Linux _disturbing_ the 
> contents of the SSD - I consider this Win-10's domain.
>Do I need to worry about this?

SATA is the wiring/controller for the internal storage, spinning or SSD.
I don't see why you should change it.  I am suspicious of the idea of some kind
of Dell RAID settings though.  Are you using or planing to use a RAID setup?

> In passing, I note the same link shows a need to disable Secure Boot - 
> is this now obsolete?

Yes, you can leave Secure Boot on, modern debian versions are fine with that.

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 08/02/2021 20:33, Cyril Brulebois wrote:

Bernard McNeill  (2021-02-08):

It says to 'Change the SATA from RAID On to AHCI, without this change Linux
will not find SSD'.
Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my
   copy of this model - so not relevant ?


Used for almost anything really, HDD, SSD, USB sticks, etc.


In passing, I note the same link shows a need to disable Secure Boot -
is this now obsolete?


Likely. We've started supporting SB with Debian 10 (buster).


Cheers,

If I change the SATA from RAID On to AHCI, do I mess up whatever is 
currently on the SSD?


Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Cyril Brulebois]

Bernard McNeill  (2021-02-08):
> It says to 'Change the SATA from RAID On to AHCI, without this change Linux
> will not find SSD'.
> Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my
>   copy of this model - so not relevant ?

Used for almost anything really, HDD, SSD, USB sticks, etc.

> In passing, I note the same link shows a need to disable Secure Boot -
> is this now obsolete?

Likely. We've started supporting SB with Debian 10 (buster).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 08/02/2021 17:03, Lou Poppler wrote:

On Mon, 2021-02-08 at 11:46 +, Bernard McNeill wrote:


On 07/02/2021 22:26, Lou Poppler wrote:

On Sun, 2021-02-07 at 15:14 -0700, Lou Poppler wrote:

On Sun, 2021-02-07 at 20:44 +, Bernard McNeill wrote:


[...]

Trial-1. Reboot, no attempt to use F12.
  Boots directly into Windows.



[...]

See install manual https://www.debian.org/releases/stable/installmanual

Also worth asking:
. Is the machine booting in BIOS mode or UEFI mode, with or without
   "Secure Boot"?  Was the machine booting in that same mode during your
   debian installation?
. Are the "disks" involved both/all partitioned in the same schema --
i.e.  GPT partitions or MBR partitions?


I forgot when writing the above, but another important question is whether you
have already disabled the Windows Fast Startup option in Windows 10.  This is
mandatory, and things will work differently depending on whether it is disabled
already or not. See section 3.6.4 of the install manual.



Fast startup was _not_ disabled - I thought (from install manual) only
applicable to Win-8, and this machine Win-10.
It is disabled now.


Good.  This is updated in the new version of the install manual, thanks to
Holger Wansing.
(see https://www.debian.org/releases/testing/amd64/ch03s06.en.html )


In the same spirit, found a 'Fastboot' option in BIOS: It was set to
'Minimal', it is now set to 'Thorough'.

UEFI mode, Secure Boot always set.

Nothing much has changed, except that reboot now offers opportunity to
skip a disk check (not taken).

I am nervous that not disabling 'Fast startup' might have messed up
process from beginning - I may repeat entire installation.


Yes worth a re-do.  Pay attention to section 6.3.7 of the install manual, about
getting the grub boot loader installed (onto your removable disk).


+++  Are the "disks" involved both/all partitioned in the same schema --
+++  i.e.  GPT partitions or MBR partitions?
I have partitioned nothing on the laptop's SSD (and don't really want to
- the idea of the external USB HDD for Debian was to make that drive a
sandbox - no possible corruption of other work under Win-10).
The external USB HDD was partitioned by the debian_installer (Guided
total disk).


This should be OK.  You said above UEFI/Secure-boot always set, which implies
that all the disks should be setup as GPT style.


FWIW I sense that in some way the 'Debian' option in the boot list
points to Win-10 on the SSD, rather than the Debian on the external HDD.
If it pointed to rubbish surely the machine would simply hang.

Best regards





I was planning the re-install, and came across this page:
https://wiki.debian.org/InstallingDebianOn/Dell/Dell_XPS_13_9360

It says to 'Change the SATA from RAID On to AHCI, without this change 
Linux will not find SSD'.
Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my 
copy of this model - so not relevant ?

   2. I don't care if Linux just 'finds' the SSD.
  But I care very greatly about Linux _disturbing_ the 
contents of the SSD - I consider this Win-10's domain.

  Do I need to worry about this?

In passing, I note the same link shows a need to disable Secure Boot - 
is this now obsolete?


Best regards

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Mon, 2021-02-08 at 11:46 +, Bernard McNeill wrote:
> 
> On 07/02/2021 22:26, Lou Poppler wrote:
> > On Sun, 2021-02-07 at 15:14 -0700, Lou Poppler wrote:
> > > On Sun, 2021-02-07 at 20:44 +, Bernard McNeill wrote:
> > 
> > [...]
> > > > Trial-1. Reboot, no attempt to use F12.
> > > >  Boots directly into Windows.
> > > > 
> > 
> > [...]
> > > See install manual https://www.debian.org/releases/stable/installmanual
> > > 
> > > Also worth asking:
> > > . Is the machine booting in BIOS mode or UEFI mode, with or without
> > >   "Secure Boot"?  Was the machine booting in that same mode during your
> > >   debian installation?
> > > . Are the "disks" involved both/all partitioned in the same schema --
> > >i.e.  GPT partitions or MBR partitions?
> > 
> > I forgot when writing the above, but another important question is whether 
> > you
> > have already disabled the Windows Fast Startup option in Windows 10.  This 
> > is
> > mandatory, and things will work differently depending on whether it is 
> > disabled
> > already or not. See section 3.6.4 of the install manual.
> > 
> 
> Fast startup was _not_ disabled - I thought (from install manual) only 
> applicable to Win-8, and this machine Win-10.
> It is disabled now.

Good.  This is updated in the new version of the install manual, thanks to
Holger Wansing.
(see https://www.debian.org/releases/testing/amd64/ch03s06.en.html )

> In the same spirit, found a 'Fastboot' option in BIOS: It was set to 
> 'Minimal', it is now set to 'Thorough'.
> 
> UEFI mode, Secure Boot always set.
> 
> Nothing much has changed, except that reboot now offers opportunity to 
> skip a disk check (not taken).
> 
> I am nervous that not disabling 'Fast startup' might have messed up 
> process from beginning - I may repeat entire installation.

Yes worth a re-do.  Pay attention to section 6.3.7 of the install manual, about
getting the grub boot loader installed (onto your removable disk).

> +++  Are the "disks" involved both/all partitioned in the same schema --
> +++  i.e.  GPT partitions or MBR partitions?
> I have partitioned nothing on the laptop's SSD (and don't really want to 
> - the idea of the external USB HDD for Debian was to make that drive a 
> sandbox - no possible corruption of other work under Win-10).
> The external USB HDD was partitioned by the debian_installer (Guided 
> total disk).

This should be OK.  You said above UEFI/Secure-boot always set, which implies
that all the disks should be setup as GPT style.
> 
> FWIW I sense that in some way the 'Debian' option in the boot list 
> points to Win-10 on the SSD, rather than the Debian on the external HDD.
> If it pointed to rubbish surely the machine would simply hang.
> 
> Best regards
> 

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 07/02/2021 22:26, Lou Poppler wrote:

On Sun, 2021-02-07 at 15:14 -0700, Lou Poppler wrote:

On Sun, 2021-02-07 at 20:44 +, Bernard McNeill wrote:

[...]

Trial-1. Reboot, no attempt to use F12.
 Boots directly into Windows.


[...]

See install manual https://www.debian.org/releases/stable/installmanual

Also worth asking:
. Is the machine booting in BIOS mode or UEFI mode, with or without
  "Secure Boot"?  Was the machine booting in that same mode during your
  debian installation?
. Are the "disks" involved both/all partitioned in the same schema --
   i.e.  GPT partitions or MBR partitions?


I forgot when writing the above, but another important question is whether you
have already disabled the Windows Fast Startup option in Windows 10.  This is
mandatory, and things will work differently depending on whether it is disabled
already or not. See section 3.6.4 of the install manual.

Fast startup was _not_ disabled - I thought (from install manual) only 
applicable to Win-8, and this machine Win-10.

It is disabled now.

In the same spirit, found a 'Fastboot' option in BIOS: It was set to 
'Minimal', it is now set to 'Thorough'.


UEFI mode, Secure Boot always set.

Nothing much has changed, except that reboot now offers opportunity to 
skip a disk check (not taken).


I am nervous that not disabling 'Fast startup' might have messed up 
process from beginning - I may repeat entire installation.


+++  Are the "disks" involved both/all partitioned in the same schema --
+++  i.e.  GPT partitions or MBR partitions?
I have partitioned nothing on the laptop's SSD (and don't really want to 
- the idea of the external USB HDD for Debian was to make that drive a 
sandbox - no possible corruption of other work under Win-10).
The external USB HDD was partitioned by the debian_installer (Guided 
total disk).


FWIW I sense that in some way the 'Debian' option in the boot list 
points to Win-10 on the SSD, rather than the Debian on the external HDD.

If it pointed to rubbish surely the machine would simply hang.

Best regards

Bug#982270: installation-reports: Installing Debian Bullseye on Cubox-i4 - installer finds no ethernet

[Rick Thomas]

Package: installation-reports
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: Followed the instruction in the README file
Image version:
https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
dated 2021-01-30 (also tried 2021-02-06)
Date: 2021-02-06

Machine: Cubox-i4P
Partitions: Didn't get that far in the installation

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ok]
Detect network card:[failed] could not proceed
Overall install:[failed ]

Comments/Problems:

I downloaded the two-part image from [1] dated 2021-01-30 and tried to 
install it on my Cubox-i4.

It booted fine but when it got to the "Detect network hardware" phase, 
it failed and said:

> No Ethernet card was detected. If you know the name of the driver 
> needed by your Ethernet card, you can select it from the list. 
> Driver needed by your Ethernet card:  

and gave a long list of available ethernet drivers, none of which seemed to be 
relevant.

I tried it again, this time with the components dated 2021-02-06.
I was hoping that the problem was transient and might have been fixed in
the intervening week, but I still got the same result: "No Ethernet card was 
detected."

Vagrant says:
> Pretty sure it is a kernel bug, since I can make it go away on a similar
> system by downgrading to linux 5.9.x. Please CC me on the report and
> I'll try to contribute what I can!

-- 

Log files attached to this report are from a successful Buster installation on 
the same hardware,
in hopes they might be some help...

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u7"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux cube 4.19.0-13-armmp #1 SMP Debian 4.19.160-2 (2020-11-28) 
armv7l GNU/Linux
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
lsmod: Module  Size  Used by
lsmod: dm_mod122880  9
lsmod: md_mod143360  0
lsmod: jfs   184320  0
lsmod: btrfs1241088  0
lsmod: libcrc32c  16384  1 btrfs
lsmod: xor16384  1 btrfs
lsmod: zstd_decompress61440  1 btrfs
lsmod: zstd_compress 159744  1 btrfs
lsmod: xxhash 20480  2 zstd_compress,zstd_decompress
lsmod: zlib_deflate   28672  1 btrfs
lsmod: raid6_pq   98304  1 btrfs
lsmod: vfat   24576  0
lsmod: fat73728  1 vfat
lsmod: ext4  618496  3
lsmod: crc16  16384  1 ext4
lsmod: mbcache16384  1 ext4
lsmod: jbd2  102400  1 ext4
lsmod: crc32c_generic 16384  6
lsmod: fscrypto   28672  1 ext4
lsmod: ecb16384  0
lsmod: brcmfmac  253952  0
lsmod: brcmutil   16384  1 brcmfmac
lsmod: cfg80211  548864  1 brcmfmac
lsmod: rfkill 28672  1 cfg80211
lsmod: usb_storage53248  0
lsmod: sd_mod 49152  3
lsmod: ahci_imx   20480  2
lsmod: libahci_platform   20480  1 ahci_imx
lsmod: libahci32768  2 libahci_platform,ahci_imx
lsmod: libata208896  3 libahci_platform,libahci,ahci_imx
lsmod: scsi_mod  196608  3 sd_mod,usb_storage,libata
lsmod: sdhci_esdhc_imx24576  0
lsmod: sdhci_pltfm16384  1 sdhci_esdhc_imx
lsmod: sdhci  53248  2 sdhci_pltfm,sdhci_esdhc_imx
lsmod: ci_hdrc_imx16384  0
lsmod: ci_hdrc45056  1 ci_hdrc_imx
lsmod: ulpi   16384  1 ci_hdrc
lsmod: ehci_hcd   77824  1 ci_hdrc
lsmod: udc_core   36864  

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

On 06/02/2021 16:42, Lou Poppler wrote:

On Fri, 2021-02-05 at 20:05 +, Bernard McNeill wrote:

This machine does not have either CD or DVD drive. Does have internal SSD.
This machine normally runs Windows-10.
Objective is to have Debian on external HDD (Toshiba), connected to
laptop via USB3.

Events:
Under Windows, downloaded iso to SSD.
Win32diskimage from SSD to HDD.
Restarted, F12, picked out HDD from bootlist, booted, got into Debian
installer.
Does a few steps (language etc).
Gets stuck at 'No common CD-ROM drive was detected'.

Ideas?


I suggest writing the installer iso to a USB stick, and booting from that to
install.  Win32diskimager should be fine for that purpose.
If you still have difficulty, please also say exactly which iso image.
Good luck.


Thank you for this.
Followed your suggestion using
debian-10.6.0-amd64-DVD-1.iso

The whole installation seemed to run to completion, but:
1. When laptop rebooted with external HDD unplugged (indeed nothing in 
either USB socket) Windows-10 booted up (expected behaviour).


2. When laptop rebooted with external HDD plugged in, and F12 pressed 
repeatedly, went into one-time boot showing both 'Debian' and 'Windows 
Boot Manager' (expected behaviour).
   Unexpected behaviour was that, on taking 'Debian' option, screen 
showed (in tiny letters)

   'Press F1 key to retry boot.
Press F2 key to reboot into setup.
Press F5 key to run onboard diagnostics.'
   Expected behaviour was to boot into Debian.

Best regards

Re: Installing Debian Bullseye on Cubox-i4 with eSATA drive... No ethernet detected

[Vagrant Cascadian]

On 2021-02-06, Rick Thomas wrote:
> On Fri, Jan 29, 2021, at 7:18 PM, Rick Thomas wrote:
>> Hi!
>> 
>> On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote:
>> > On https://www.debian.org/devel/debian-installer/
>> > you should look under the daily snapshots.
>> > For armhf that would be
>> > https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>> 
>> I downloaded the two-part image from [1] dated 2021-01-30 and tried to 
>> install it on my Cubox-i4.
>> 
>> It booted fine but when it got to the "Detect network hardware" phase, 
>> it failed and said:
>> 
>> No Ethernet card was detected. If you know the name of the driver 
>> needed by your Ethernet card, you can select it from the list. 
>> Driver needed by your Ethernet card:  
>> and gave a long list of available ethernet drivers.
>> 
>> I couldn't find anything that looked like an Atheros 8035 driver, which 
>> seems to be the one in use when I boot with a working system.
>> 
>> Any suggestions?
>> Thanks!
>> Rick
>> 
>> [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>>  dated 2021-01-30
>
> I tried it again, this time with the components dated 2021-02-06 (today).
> I was hoping that the problem was transient and might have been fixed in the 
> intervening week, but I still got the same result: "No Ethernet card was 
> detected."
>
> Do I need to file a bug report?  If so, to which package?  If I do, is there 
> any chance it will be fixed before Bullseye is released into the wild?
> Is there a known workaround that I can apply?

Pretty sure it is a kernel bug, since I can make it go away on a similar
system by downgrading to linux 5.9.x. Please CC me on the report and
I'll try to contribute what I can!


live well,
  vagrant


signature.asc
Description: PGP signature

Re: Installing Debian Bullseye on Cubox-i4 with eSATA drive... No ethernet detected

[Rick Thomas]

On Fri, Jan 29, 2021, at 7:18 PM, Rick Thomas wrote:
> Hi!
> 
> On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote:
> > On https://www.debian.org/devel/debian-installer/
> > you should look under the daily snapshots.
> > For armhf that would be
> > https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
> 
> I downloaded the two-part image from [1] dated 2021-01-30 and tried to 
> install it on my Cubox-i4.
> 
> It booted fine but when it got to the "Detect network hardware" phase, 
> it failed and said:
> 
> No Ethernet card was detected. If you know the name of the driver 
> needed by your Ethernet card, you can select it from the list. 
> Driver needed by your Ethernet card:  
> and gave a long list of available ethernet drivers.
> 
> I couldn't find anything that looked like an Atheros 8035 driver, which 
> seems to be the one in use when I boot with a working system.
> 
> Any suggestions?
> Thanks!
> Rick
> 
> [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>  dated 2021-01-30

I tried it again, this time with the components dated 2021-02-06 (today).
I was hoping that the problem was transient and might have been fixed in the 
intervening week, but I still got the same result: "No Ethernet card was 
detected."

Do I need to file a bug report?  If so, to which package?  If I do, is there 
any chance it will be fixed before Bullseye is released into the wild?
Is there a known workaround that I can apply?

Thanks for any help!
Rick

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Lou Poppler]

On Fri, 2021-02-05 at 20:05 +, Bernard McNeill wrote:
> This machine does not have either CD or DVD drive. Does have internal SSD.
> This machine normally runs Windows-10.
> Objective is to have Debian on external HDD (Toshiba), connected to 
> laptop via USB3.
> 
> Events:
> Under Windows, downloaded iso to SSD.
> Win32diskimage from SSD to HDD.
> Restarted, F12, picked out HDD from bootlist, booted, got into Debian 
> installer.
> Does a few steps (language etc).
> Gets stuck at 'No common CD-ROM drive was detected'.
> 
> Ideas?

I suggest writing the installer iso to a USB stick, and booting from that to
install.  Win32diskimager should be fine for that purpose.
If you still have difficulty, please also say exactly which iso image.
Good luck.

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Holger Wansing]

Hi,

Bernard McNeill  wrote:
> This machine does not have either CD or DVD drive. Does have internal SSD.
> This machine normally runs Windows-10.
> Objective is to have Debian on external HDD (Toshiba), connected to 
> laptop via USB3.
> 
> Events:
> Under Windows, downloaded iso to SSD.
> Win32diskimage from SSD to HDD.
> Restarted, F12, picked out HDD from bootlist, booted, got into Debian 
> installer.
> Does a few steps (language etc).
> Gets stuck at 'No common CD-ROM drive was detected'.

Why not use an USB stick as installation media, as documented here:
https://www.debian.org/CD/faq/#write-usb


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Geert Stappers]

On Fri, Feb 05, 2021 at 10:32:44PM +, Bernard McNeill wrote:
> On Fri, Feb 05, 2021 at 08:05:22PM +, Bernard McNeill wrote:
> > This machine does not have either CD or DVD drive. Does have internal SSD.
> > This machine normally runs Windows-10.
> > Objective is to have Debian on external HDD (Toshiba), connected to laptop
> > via USB3.
> >
> > Events:
> > Under Windows, downloaded iso to SSD.
> > Win32diskimage from SSD to HDD.
> > Restarted, F12, picked out HDD from bootlist, booted, got into Debian
> > installer.
> > Does a few steps (language etc).
> > Gets stuck at 'No common CD-ROM drive was detected'.
> >
> > Ideas?
> >
>
> Is there any chance this is related to Bug #981666?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981666
> "cdrom-detect: Preseeding cdrom-detect/load_media and a high-enough priority 
> lead to failure"

Nope, that issue is about preseeding.



Please pursuit your objective, you will be rewarded with usefull knowledge.


Use https://www.debian.org/releases/stable/amd64/apas04.en.html
as guidance for further steps.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

Is there any chance this is related to Bug #981666?

Best regards

Problem installing Debian on Dell XPS 13 9360 laptop

[Bernard McNeill]

This machine does not have either CD or DVD drive. Does have internal SSD.
This machine normally runs Windows-10.
Objective is to have Debian on external HDD (Toshiba), connected to 
laptop via USB3.


Events:
Under Windows, downloaded iso to SSD.
Win32diskimage from SSD to HDD.
Restarted, F12, picked out HDD from bootlist, booted, got into Debian 
installer.

Does a few steps (language etc).
Gets stuck at 'No common CD-ROM drive was detected'.

Ideas?

Best regards

Bug#969516: Please support installing onto f2fs root filesystem

[Stephan Lachnit]

> I would be willing to sponsor this but I'm not sure whether such
> a change would be a good idea a little over a week from the soft
> freeze.

Can you sponsor the upload [1] already? This won't add the package
to the installer, but we will decide to have it include in bullseye
(which I really hope), we better upload it ASAP to NEW.

Regards,
Stephan

[1] https://mentors.debian.net/package/partman-f2fs/

Re: Bug#969516: Please support installing onto f2fs root filesystem

[John Paul Adrian Glaubitz]

On 2/4/21 8:16 PM, Stephan Lachnit wrote:
>> I would be willing to sponsor this but I'm not sure whether such
>> a change would be a good idea a little over a week from the soft
>> freeze.
> 
> Can you sponsor the upload [1] already? This won't add the package
> to the installer, but we will decide to have it include in bullseye
> (which I really hope), we better upload it ASAP to NEW.

Has anyone reviewed the package yet and has there been any input from
other d-i maintainers? I think at least KiBi should give his OK whether
he wants to introduce such a change this late in the release process.

FWIW, someone already tried to upload it without prior coordination
on this mailing list but the upload got rejected because that person
just has DM rights. It's not really okay to make such uploads without
coordination with the d-i team when we're just before the Bullseye
release - although I understand the motivation.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913