Bug#1032374: installation-reports

[Florian Zimmermann]

Thanks Holger!

 >  GRUB_DISABLE_OS_PROBER=false

this works now with GRUB showing both Win and Debian/GNU. And both boot 
fine, pfew.
In the meantime before fixing the above, in my case I had a BIOS option 
"UEFI Hard Disk Drive BBS Priorities",
that allowed me to find the Debian partition and could start from there 
"manually".
I was so glad I labelled it "debian" during the manual partitioning so I 
could find it! :-)

Three other observations (and I hope the mailing list is still OK to use 
here? Newbie here).

1) I tried Debian 11.6 after no success with 12 in-between. For 11.6 
after manually partitioning,
the installer said something along "No EFI partition found, please go 
back". I had a EFI Windoze partition, so
I guess the installer was smart enough to not be allowed to touch that 
one. But the Debian 12 installer did not show this warning at all!

2) the main user not being in the "sudo" group and adding it manually I 
find quite user-unfriendly...

3) After the first boot, I checked with "top" and no activity! This is 
in great contrast to other distros,
that fill in their (useless) databases and what not after the 1st boot. 
Very responsive system from the get go! :-)

Thanks,
  Florian

On 3/5/23 15:27, Holger Wansing wrote:
> Hi,
>
> Holger Wansing <hwansing at mailbox.org> wrote (Sun, 5 Mar 2023 15:02:28 +0100):
>> mindfsck <mindfsck at gmail.com> wrote (Sun, 5 Mar 2023 12:16:48 +0100):
>>> Package: installation-reports
>>>
>>> Boot method: USB stick
>>> Image version: debian-bookworm-DI-alpha2-amd64-netinst.iso
>>> Date: 2023/03/05
>> [...]
>>> Comments/Problems:
>>> The PC contained a full-sized Windows 10 partition, so I resized this
>>> in Debian installer. After successful Debian installation,
>>> the reboots never resulted in landing into GRUB, but rather Windows is
>>> loaded :-(
>>>
>>> Can I manually solve this?
>> This has already been reported several times, sadly. For example
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031594
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012865
>>
>> Re-assigning both above bugs to grub.
>>
>>
>>
>> @mindfsck: you should be able to fix your problem like this:
>> - as root, edit /etc/default/grub: find a line like
>> 	#GRUB_DISABLE_OS_PROBER=false
>>    Change it into
>> 	GRUB_DISABLE_OS_PROBER=false
>>    (means: remove the # at the beginning of the line.)
>>
>> - as root, execute "update-grub"
>>
>> This should find your Windows installation and add an entry to the
>> bootloader menu, to boot Windows.
>
> Uups, sorry, I misread your report.
> Your problem is, you can only boot Windows, and NOT boot Debian.
> I mixed that up with reports, where a start entry for Windows is missing
> in the grub menu.
>
>
>
> In your case, my best guess would be, to start the debian-installer
> again, but from the installer menu choose the "Rescue" entry, to not perform
> another installation, but start a recovery environment, where you get the
> possibility to fix such things.
>
> There, mount the corresponding partition (the partition, where you installed
> Debian on; I guess this might be /dev/sda2) as /root, and then do similar
> as written above:
> execute "TERM=bterm nano /etc/default/grub"
> to make a line containing "GRUB_DISABLE_OS_PROBER=false" in that file
>
> Then call "update-grub".
>
> Please report, how it goes.
>
>
> Holger
>