Received: from mail-lf1-f68.google.com (mail-lf1-f68.google.com [209.85.167.68]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id E8B76781901 for ; Mon, 10 Feb 2020 16:59:17 +0000 (UTC) Received: by mail-lf1-f68.google.com with SMTP id 9so4686999lfq.10 for ; Mon, 10 Feb 2020 08:59:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=hV2F418KZCn+gUZQ2zSfLJ4sqfZbLEfYFreAX26WF10=; b=FWa6XYK7hbrtYuagCpsBmL2ZbM8ghYGUMhQ/fCqE/9I3EACl5s2JUYu4eTBAt4sF8+ u9oZtHC5OuNPmC7z7Wr+seFDMLjQ7iMZO1CJt3FeyaNdgwEEcEM53h0CTBwyWKbvIaC2 8YGbpg9h+F9FGHQUPqEQjxy5Z+eVomYNenl5Yx4sxGgPXaieAHj+RXG/C7wqzFl99oJY pCC+yCk8mSBtoCfufIcd2N5v93dRjvkqSf2niOUpTcRjDu8FmHbvE6wjoX/vXX1cq/Xu 7Jz0N4VLUP5ZuvuaUwyEgxtTskUfoUhwe1zPlNUUt9YJ4u+VhN6tygTKug2hGvNSBcsU CHpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=hV2F418KZCn+gUZQ2zSfLJ4sqfZbLEfYFreAX26WF10=; b=XTmvIxai7nNVezDQqYYAUDaKzT08GzC0xStjd76Dnn+qzI08e5W49yeAKwr3he659s NP+PHyhqmNRS0PVWl4RuFp+vy/0m+RsWM/ws168MgQcQ/B+umFDVXq4esIKi5VQft+r8 L2p5UpY5BoQGgK93mEZb94mzlxjv4p/q3JPbgSzoCCOXT5DzljEIwIlqdzCyav2QiYn9 Mu6c5wZyF6sxR/R/s8lTX9Us1sYwtaKQLw0+NaXQt1DhG2gLimNkCWnzPPSHTsexNPu5 3NLs3nxygn+4Fw5JKJyJIkLeUPsGva7cRJET/pQXCrFVI3Xsi2yebhRJNNjmU+Ym7NBX Z4Ig== X-Gm-Message-State: APjAAAUooyJaTkuh1GaOBtN0RxKRmUOM/nSyR8H5XMNvewipk5MH7HUg gwSXqexuWpoxbQEnOm4r6VpVsWPc9I1kJodCyUQ= X-Google-Smtp-Source: APXvYqxQVlqVBynHLBvWtXnOSDwOvKCet2GCQu4dtpDmx5efpMrqZuHnCzRGWOQGhicr05VD6Rz2uJBNzrZhOYvUBWE= X-Received: by 2002:a19:5503:: with SMTP id n3mr276074lfe.136.1581353956830; Mon, 10 Feb 2020 08:59:16 -0800 (PST) MIME-Version: 1.0 References: <4{e.5jkq4.3e}oy1c{aK3.1UGND4@seznam.cz> <56H.5jkqE.3ZoR0Dxqmmf.1UGOMk@seznam.cz> In-Reply-To: <56H.5jkqE.3ZoR0Dxqmmf.1UGOMk@seznam.cz> From: PICCORO McKAY Lenz Date: Mon, 10 Feb 2020 12:28:19 -0430 Message-ID: Subject: Re: Alpine Linux question To: "Ing. Jiri Ullmann" , alpine-user Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El lun., 10 de feb. de 2020 a la(s) 12:02, Ing. Jiri Ullmann (jullmann@post.cz) escribi=C3=B3: > Hello Lenz, yes, this happen only with Alpine Linux. In that UEFI setup i= s except of boot order nothing to configure and AS i guess, there are some UEFI have the option of disabling the safe boot but there's small ones that really it have a pseudo option, which does not disable it completely as in the case of the last magellanic minilaptops (canaimites) from Argentina and Venezuela... > harddrive I have on the first upper position, so it should work. But ther= e is no record about UEFI file to boot. https://wiki.alpinelinux.org/wiki/Alpine_and_UEFI#Notes_about_the_boot_flag= s_and_boot_partition AS you said.. boot relies on the partitions scheme as i write in the wiki (the only man that takes the most important taks to avoid those problems of miscinformation) BUT: https://wiki.alpinelinux.org/wiki/Alpine_and_UEFI#What.27s_this_infamo= us_.22Secure_Boot.22.3F as i tell you there's some that have a speudo option.. in those "magallanes" mini laptops i must only can install winbuntu, debian and guinddd.. argggg dos.. that due need a very specific corret scheme partition with a specific firmware files as explained here https://wiki.alpinelinux.org/wiki/Alpine_and_UEFI#Alpine_disk_layout_for_UE= FI IT's har to do that i understant you, but are very bad when developer dont write their documentations and users must guess all the things > Sad World with UEFI. > > > -- > Ing. Ji=C5=99=C3=AD Ullmann > jullmann@post.cz > +420-607-542442 > *** ISYS / Alpine Linux 3.11.3 *** > > > ---------- P=C5=AFvodn=C3=AD e-mail ---------- > Od: PICCORO McKAY Lenz > Komu: Ing. Jiri Ullmann > Datum: 10. 2. 2020 16:20:31 > P=C5=99edm=C4=9Bt: Re: Alpine Linux question > > hey Jiri, that problem only happened on alpine linux? i mean, seems in > your UEFI BIOS maybe there's another boot order or config that > prevents to boot it > > similar problem happened in the https://t.me/alpine_linux telegram group > > > Lenz McKAY Gerardo (PICCORO) > http://qgqlochekone.blogspot.com > > El lun., 10 de feb. de 2020 a la(s) 10:44, Ing. Jiri Ullmann > (jullmann@post.cz) escribi=C3=B3: > > > > Dear Friends, > > > > I am very, very, VERY satisfied user of your Alpine Linux. Because I am= a pretty Old-School linux user, > > so I have for my distro such specific demads: > > > > - Text only distro (without gui) > > - Not live, but installable distribution image > > - Not systemd utilization (openRC is completely nice alternative for me= ) > > - Small size (if possible ideal up to max. 1GB) > > > > These all of them is Alpine Linux greatly satisfiing and I must say big= THANKS TO YOU! for your great work. > > All of you are bringing true spirit of computing to my life and work, b= ecause graphical machines are not my cup of tea > > and for my kind of computing I do not need Windows nor Big Linux distro= =E2=80=A6 > > > > Unfortunately with new set of my hardware came devices, whose have UEFI= only firmware (without CMS module) and I > > have serious troubles to install Alpine Linux on them. As hardware prod= ucers are switching to UEFI class 3 and dropping legacy BIOS interface (CMS= ), incidence of problems is growing. Please, if you have such idea, help me= in my troubles. > > > > What is the object of trouble: > > Installation of Alpine Linux Extended Image version 3.11.3 on computer,= which is UEFI only capable. > > What happened: > > ISO with Alpine Linux (extended) 3.11.3 booted properly and I got first= start root prompt (as many times before) > > I have done usual mantra, so export BOOTLOADER=3Dgrub then setup-alpine= , walk through questions as usual and > > installation has begun. During installation nothing wrong (visualy) hap= pened, no extra error messages etc=E2=80=A6 BUT, > > after rebooting and removing installation media system want not to boot= and in UEFI boot order list is not present any record leading to Alpine Li= nux. > > What I have checked: > > - Double checked if SecureBoot is OFF, it was first idea, which I had, = but SecureBoot was really OFF > > - Boot again from CD and mount partitions from harddrive (EFI, SYS and = SWAP) partitions were present, in EFI partition > > existing alpine and boot subfolders with appropriate bootx64.efi and gr= ubx64.efi files were existing and look without > > problem. > > - The same installation CD I tried on another UEFI only computer and it= work without trouble > > - I have tried on device, with which I have troubles another distro (ub= untu) and it worked perfectly, but UBUNTU is not > > the right one, I want to use... > > - I have not possibility from UEFI setup environment find and assign bo= ot file to boot menu... This version is lack of this option. > > - I walked through your FAQ and WIKI and (maybe wrong searching), but d= id not find any info, which will give me a chance > > to try something another. > > - I am afraid, that it is something wrong with writing values to the EF= IVARS, but I am not so much familiar with them in > > ALPINE, because up to this time everything gone seamless. Please have y= ou such trick and/or advice how to deal with this trouble? I really want no= t to give up with Alpine Linux on that maschine. > > > > Thank you a lot in advance for your time and answer. > > > > Your big fan from Czech Republic > > > > Jiri Ullmann > > > > > > -- > > Ing. Ji=C5=99=C3=AD Ullmann > > jullmann@post.cz > > +420-607-542442 > > *** ISYS / Alpine Linux 3.11.3 *** > >