Rob - see below, you might want to subscribe to the bug too.
Suggestion is to use firmware .iso and a more verbose dd line to ensure
you've actually written the whole image correctly.
Also, I would suggest enabling TPM and secure boot unless you are *absolutely*
sure that you don't need them. Sec
On 17 November 2022 21:33:33 GMT, "Adam D. Barratt"
wrote:
>Hi,
>
>We've managed to slip behind on getting a bullseye point release
>sorted, again. :-( I realise we're heading towards the holidays at a
>surprising rate of knots, but hopefully we can find a generally
>agreeable date.
>
>Please cou
Thanks, after messing with it for quite awhile, I finally got it to work with
the standard ISO.
I booted with the Arch live image and did:
wipefs -a /dev/nvme0n1
dd if=/dev/zero of=/dev/nvme0n1 bs=512 count=10
then I used efibootmgr to delete all existing entries.
Once I did that, the neti
Hi Rob,
I see Andy has been helping you!
On Sat, Nov 19, 2022 at 03:38:33PM +, r...@tekhax.io wrote:
>Thanks, after messing with it for quite awhile, I finally got it to work with
>the standard ISO.
>
>I booted with the Arch live image and did:
>
>wipefs -a /dev/nvme0n1
>dd if=/dev/zero of=/
On Thu, 2022-11-17 at 21:33 +, Adam D. Barratt wrote:
> Please could you indicate your availability and preferences between:
>
> - December 3rd
No time here.
> - December 10th
> - December 17th
These are still free.
Ansgar
Thanks for the detailed message. I started everything over to try to reproduce
the problem.
I wiped out the NVMe drive again (wipefs -a and dd if=/dev/zero of=/dev/sdb
bs=512 count=10), and re-installed Pop!OS 22.04 non-NVidia version, which
was successful. The computer was operating normal
6 matches
Mail list logo
