--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: installation-reports: Successful install on Acer Switch V 10 (SW5-017P)
- From: Rudolf Polzer <divVerent@gmail.com>
- Date: Fri, 05 Nov 2021 17:47:27 -0400
- Message-id: <163614884777.2971.17648314506265155766.reportbug@doesntlol>
Package: installation-reports
Severity: normal
X-Debbugs-Cc: divVerent@gmail.com
Boot method: USB
Image version: firmware-testing-amd64-netinst.iso
Date: 2021-10-10
Machine: Acer Switch V 10 (SW5-017P)
Partitions:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 1050MB 512MB ext2 boot
3 1050MB 62.5GB 61.5GB crypt
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [X]
Detect network card: [X] (needed firmware-iwlwifi)
Configure network: [X]
Detect media: [X]
Load installer modules: [X]
Clock/timezone setup: [X]
User/password setup: [X]
Detect hard drives: [X]
Partition hard drives: [X]
Install base system: [X]
Install tasks: [X]
Install boot loader: [E]
Overall install: [X]
Comments/Problems:
Primary problem was that the installed system did not boot. This is a known
problem of some Acer UEFI firmwares, which have hardcoded the path where
Windows puts its boot loader and instead ignore the EFI variables.
To fix this, I had to move all .efi and .CSV files from
/target/boot/efi/EFI/debian to /target/boot/efi/EFI/Microsoft/Boot and
rename shimx64.efi to bootmgfw.efi.
This can be done in the final stage of the installer right before the
reboot.
See https://hansdegoede.livejournal.com/24132.html
--- End Message ---
--- Begin Message ---
Hi,
Bug #1006809:
Bernhard <bernhard.woerner@posteo.de> wrote (Sat, 05 Mar 2022 16:14:39 +0000):
> Installation was successfully.
> I think, it's time for the first Alpha version for Debian 12 :-)
>
Bug #1010701:
Bernhard <bernhard.woerner@posteo.de> wrote (Sat, 07 May 2022 16:56:27 +0000):
> Installation was successfully.
> No problems detected.
Bug #1004550:
Bernhard <bernhard.woerner@posteo.de> wrote (Sun, 30 Jan 2022 11:39:10 +0000):
> Comments/Problems:
>
> No problems detected.
> Installation was successfully.
Bug #998661:
Rudolf Polzer <divVerent@gmail.com> wrote (Fri, 05 Nov 2021 17:47:27 -0400):
> Comments/Problems:
>
> Primary problem was that the installed system did not boot. This is a known
> problem of some Acer UEFI firmwares, which have hardcoded the path where
> Windows puts its boot loader and instead ignore the EFI variables.
>
> To fix this, I had to move all .efi and .CSV files from
> /target/boot/efi/EFI/debian to /target/boot/efi/EFI/Microsoft/Boot and
> rename shimx64.efi to bootmgfw.efi.
>
> This can be done in the final stage of the installer right before the
> reboot.
>
> See https://hansdegoede.livejournal.com/24132.html
Bug #1004552:
"Charles Champness (TheRedRightHand)" <wildwasser@gmail.com> wrote (Sun, 30 Jan 2022 13:30:17 +0100):
> Comments/Problems: Install worked flawlessly with firmware-11.2.0-amd64-DVD-1.iso
>
> I was quite worried about the install (and purchase of the NUC), because there is practically NO information about installing any linux bistro on the Intel generation 11 NUCs, and they’re a perfect headless home server with a 2.5GBe network connection. I only found reports of issues from installs during 2021… nobody reports the successful installs, only the problems.
[...]
> I’d be really happy if you can add the NUC11TNKv5 to the list of successful installs, even if I had to use the non-free image, I am VERY happy with this system, thanks to the entire Debian community! :)
Closing "successful" bugs
Thanks for your reports!
--
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---