Installation fails on BIOS/MBR partitioning (grub-pc issue?) #265
Replies: 28 comments 24 replies
-
|
first, thanks for your message: I share almost all your ideas about the need of eggs for a penguins' tribe! I will check tomorrow your problem, but as far as I know - I usually test on VMs BIOS or UEFI, but mostly BIOS and I don't have such problem. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for getting back to me so quickly. If I'm doing something wrong,
I'm happy to get educated. I'm not a developer......just a "hack" trying
to figure out your wonderful tool.
And like I said, working great for my UEFI/GPT setups. It's my BIOS/MBR
installs giving me fits. Any advice appreciated!
…On Wed, Aug 16, 2023, 5:56 PM Piero Proietti ***@***.***> wrote:
Hi @JamesShriner <https://github.com/JamesShriner>
first, thanks for your message: I share almost all your ideas about the
need of eggs for a penguins' tribe!
I will check tomorrow your problem, but as far as I know - I usually test
on VMs BIOS or UEFI, but mostly BIOS and I don't have such problem.
—
Reply to this email directly, view it on GitHub
<#265 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BB6QHRGA6YMT5L7SGHMBDFTXVU6XLANCNFSM6AAAAAA3SRJ35Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
this morning I just remastered Parrot OS home, and I tested it on a VM bios. Really I did that for Parrot OS security too, but is big enought, can you try di dowonload it an test on your BIOS machine? You can find it here.
Another temps we can make, if you can share your image, I can try to install it here. Let me to know. |
Beta Was this translation helpful? Give feedback.
-
|
Piero, I downloaded your Parrot ISO and installed as a VM, using Virtual Machine Manager (VMM) on my Debian 10 base OS. Using a BIOS boot, and a MBR partition scheme, your Parrot ISO installed with no issues whatsoever. I noted that Calamares on Parrot was running "as superuser". What other changes (if any) were present in that version of Calamares and/or your Parrot ISO? Considering that my Penguins Eggs ISO installs just fine in UEFI/GPT configuration, but fails in BIOS/MBR config; and considering that YOUR ISO installs just fine in BIOS/MBR configuration, it begs the question...."why won't MY ISO install in BIOS/MBR configuration" without throwing the installation errors in the previously provided log file? I uploaded my Penguins Eggs created ISO for you to inspect & analyze. Do you see any issues? Have I found a bug, or perhaps a perfect combination of factors that prevents the installation in BIOS/MBR? Or am I just doing something wrong with your tool? Please advise! |
Beta Was this translation helpful? Give feedback.
-
|
Good morning James, I'm just trying to download your ISO but cannot find from where! Please send me the link. |
Beta Was this translation helpful? Give feedback.
-
|
Apologies, I previously replied to your email, but I see I replied to "[email protected]". Here's a copy of previously sent e-mail, with link: Piero, Happy to share my ISO with you and have you diagnose the issue. Google blocks ISO attachments as "potentially harmful", so I've uploaded to my Google Drive, and provided link for download. User is "live" and Password is "password". https://drive.google.com/file/d/1D8LM7cdd0OgWcL0dYjnygIGg72GXavON/view?usp=drive_link This is an "all-inclusive" distro with every tool imaginable for MY personal use-cases, so it's rather large...about 3.5GB. Let me know when you have downloaded the ISO, so I can take it back down and re-claim my Drive space. LOL! Thank you in advance for any insight and guidance you can provide! |
Beta Was this translation helpful? Give feedback.
-
|
OK, just installing - at the moment on UEFI - later I will try BIOS- Nice look!
|
Beta Was this translation helpful? Give feedback.
-
|
Trying to install on bios we have this error, probably don't find the local repository yolk
I will try to install it on UEFI, then I will remaster it again to see if the problem persist. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I installed successfully on UEFI, then: This will ugrade everything, add eggs repository so you will have eggs v9.5.17 the actual one Then reboot and removed old kernels: Now we need to reconfigure eggs with new kernel, the shortest way is: And edit /etc/penguins-eggs/eggs.yaml to replace prefix with At this point I produced again, with a new yolk: Now will see that happen |
Beta Was this translation helpful? Give feedback.
-
|
can't understand... I suppose you used some repos from spirallinux, actually disabled. But was not able to install on BIOS after 3 or more remasterizations... Francly, I don't know why. I will try again later Perhaps can be usefull if you come in https://t.me/penguins_eggs to can chat |
Beta Was this translation helpful? Give feedback.
-
|
Dear James unfortunately, I don't have good news for you, I have tried to update/modify your system in more than one way, but I couldn't get anything done. What puzzles me is the fact that the system itself sometimes crashes, window frames do not appear, etc. I also installed the system on BIOS using the I don't have an exact answer, alas, but I'm afraid you may have messed up the dependencies, perhaps by using spirallinux and then removing it. I can't tell you much more than that, don't hold it against me. My advice, since this is probably your first experience, is to start from scratch, from a clean Debian bookworm base and install the programs you need as you go. Happy hacking! |
Beta Was this translation helpful? Give feedback.
-
|
After seeing your system I tried to create a simple base for you with lxqt, eggs and calamares. The name is egg-of-debian-bookworm-lxqt, you can download and install it with calamares, you might just need it as a starting point if you are not comfortable starting from a CLI interface. Happy hacking again https://sourceforge.net/projects/penguins-eggs/files/ISOS/debian/bookworm/ |
Beta Was this translation helpful? Give feedback.
-
|
as a matter of exercise, I'll probably do that. I was using Spiral, based on Debian 11, because Spiral did some of the customizations that I normally would've done myself....so it was a "head start" on the customizations. Other than that, Spiral is 100% Debian, with only Debian repos. https://spirallinux.github.io/ But Debian 12 now allows non-free firmware, so that may make Spiral irrelevant now. BTW....Spiral installs just fine to a BIOS/MBR config using Calamares, so I'm pretty sure it's something I have done. But I'm at a loss.... Probably start over with a Bookworm base, enable non-free repos, and try again. Thanks for taking a look! |
Beta Was this translation helpful? Give feedback.
-
|
Piero, Your link above for "egg-of-debian-bookworm-lxqt" takes me to your Debian>Bookworm page, but no lxqt version. most recent is "naked" from 1 hour ago. FWIW... |
Beta Was this translation helpful? Give feedback.
-
|
No, now the image there is... take a bit uploading it and another bit to be visible on sourceforge. Well, in the while I discovered who the problem is not in your distro - I'm talking about the problem to install on BIOS - but in my code! In same point I introduced a bug in the local repository where I have just the necessary for boot, to be able to install without internet. So, at this point happy haking to... myself! |
Beta Was this translation helpful? Give feedback.
-
|
aha! that makes sense! will you be modifying your code to allow for that? I'm happy to test for you with my remastered egg! You may have just saved me several days of work remastering Debian-Bookworm-LXQT from its base config! |
Beta Was this translation helpful? Give feedback.
-
eggs-9.5.18
That happenThis solve your problem and mine! The error arise when local repo yolk was made on BIOS - always when I release - and is remastered on UEFI withour re-create yolk. It depend on the fact who yolk icontain packages for UEFI but not packages for BIOS. This result in an error installing on BIOS. And can happen also the opposite. I changed the way yolk work: now it work without excluding packages already installed, so create yoik on UEFI or on BIOS lead to the same result. Thanks for the report, I never realized it but I think it gave several users problems. |
Beta Was this translation helpful? Give feedback.
-
|
I'm noting in "eggs dad" a message about "using pre-existing yolk", so tried "sudo eggs tools yolk" to make sure the yolk is updated to work with the 9.5.18 DEB. After that, ran "eggs dad -d" to ensure reset to defaults; then ran "eggs dad" again to input MY selections. I note that "eggs dad" produces a "first taste" of ISO. But "eggs produce" also produces an ISO. What is the difference between those tools? And what is the recommended use-case scenario for both? Can I use the ISO from "eggs dad", or should I be using "eggs produce" for an ISO? |
Beta Was this translation helpful? Give feedback.
-
|
i've also tried "eggs produce -y" to force the use of the updated yolk. Also results in failure to install, with the same message. What am I missing? |
Beta Was this translation helpful? Give feedback.
-
|
eggs dad is just a shorcut to create an iso with just a command, at last it call eggs produce. Actually I use a lot When you begin to have practice with eggs, it is convenient to use Perhaps this two are the most important:
|
Beta Was this translation helpful? Give feedback.
-
|
Cannot believe, but I will test your iso again! :-( |
Beta Was this translation helpful? Give feedback.
-
|
please do. i'm scratching my head again over here. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I installed your system in a UEFI virtual machine, then:
add ppa for eggs, to not be bored to download from sourceforce.
eggs will be updated to last version, and the previous yolk is removed
Now I use the produced iso to install on a VM BIOS
And I hope, and think it will work... but let me to check again... Nothing to do... we have again the same problem! Quite strange, and I can't explain, but the reality have a superior level than the inferences. |
Beta Was this translation helpful? Give feedback.
-
|
You can try yourself! In spiral there are a lot of good ideas, but it's long time I don't use/remaster It. |
Beta Was this translation helpful? Give feedback.
-
|
OK, this morning I renew same versions of my SpiralLinux remaster:
As I saw trying xfce the problem here persist - the picture is for cinnamon, made from UEFI and trying to install on BIOS - but yet don't understand the reasons.
Download it from here |
Beta Was this translation helpful? Give feedback.
-
|
hmmm....I also attempted an egg from Spiral LXQT (v11.2 on his download page) and it failed. I was inclined to believe that the Spiral base was the problem, and am attempting a vanilla Debian 12.1 egg as a test case. In the meantime, you indicate you were successful with Spiral LXQT?! That makes NO SENSE that yours would succeed, but mine would fail (with the same error that we keep seeing). What the heck? |
Beta Was this translation helpful? Give feedback.
-
|
okay....success creating an egg from Debian12 LXQT, as downloaded from Debian; installs on UEFI and MBR partition schemes. So it's not me, LOL! I did note that the Live session displays my name as the default user, rather than LIVE, but I can change the user to LIVE and then the password works. So I'm calling that a success, with possibly an error on my part configuring the user with "eggs dad". I also note that default LXQt uses SDDM as display manager, rather than LightDM or GDM, which is the default in most distros. Spiral LXQT uses LightDM, so maybe that's a clue? I imagine XFCE would use LightDM or GDM, so maybe it's not a clue after all? With that said, I'm now looking at Spiral as the source of error, but I can't reconcile the fact that YOU were successful with Spiral LXQT and mine fails spectacularly. But then your Spiral XFCE egg failed. So it seems to be Spiral related, but no apparent consistencies between versions of distros? I think I'm going to just chalk up my experience to "MY distro is a UEFI/GPT ONLY installation". That shouldn't be terribly limiting in my world, as I imagine most or all of my machines are UEFI implementations. My OCD tendencies still want to "fix the problem", but it's just not revealing itself yet. I'm hoping the path will reveal itself with more time and experience(s). And I'm hoping your eyes, as developer, may spot something. If you do, and you need a BETA tester, hit me up. I think your project is sorely needed in Linux, and I'm happy to help out in whatever way I am capable. THANK YOU for this tool! |
Beta Was this translation helpful? Give feedback.
-
|
Piero, I was checking out your remastered eggs of Spiral and saw your note of recommended installation via "sudo eggs install -u" for unattended access, due to unresolved issues, which I assumed were the Calamares issues we're running down. FWIW, I am able to install my remastered distro to BIOS/MBR using your suggested method via eggs installer! Unfortunately, the distro installs with user=artisan and password=evolution. So I tried again with just "sudo eggs install" and changed the username and password to my preferences. While the system installed, there was no user to select (only "Other...) and no combination of users & passwords would work. I had assumed the referenced unresolved issue was Calamares, but realized it was an issue with the eggs installer. (side note: is this the KRILL installer, or an 'eggs installer'?) Long story short....I re-installed with "sudo eggs install -u", rebooted into newly installed BIOS/MBR scheme, and logged in as artisan/evolution; then created a new user for myself with sudo privileges. Rebooted again, and successfully logged in as myself as user; updated repos, installed a few packages for sport, and then removed them. I then deleted the user artisan. Until we figure out the Calamares and/or eggs installer(?) issues, this is an acceptable workaround for me! A PITA, for sure, but a working installation....for an installation scheme that likely won't happen very often! I've described the steps taken in case there's a clue in there somewhere to assist with troubleshooting. So while we haven't truly resolved the issue, we have found a workaround that is a viable option for what I expect to be a rare use-case scenario. Can't thank you enough for your troubleshooting assistance....would never have gotten here without you! VERY MUCH APPRECIATE YOU, your efforts, and PenguinsEggs! |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if my issue is related or not. But it seems my respin's installation is not installing the bootloader. Every time I install on real hardware so far, it thinks the drive the system is installed to isn't bootable. My system is based on MX Linux. So I can at least use the MX Boot Repair to fix the problem. But that's not ideal. You may be wondering why I'm not using the MX Snapshot tool. Well it doesn't really offer the same level of customization in the installation process as Penguins-Eggs does. So I've decided to go with this. But it sure doesn't want to install that bootloader for some reason. BTW, I've tried my UEFI/BIOS in Legacy, UEFI Hybrid, and UEFI Native. It doesn't boot in any of those. The fix for me right now is running MX Bootrepair and reinstalling GRUB to ESP. If there is something I'm missing, let me know. I'll upload my ISO ASAP. I will say when MX Bootrepair is on the ISO, I will get this error. Command /usr/sbin/bootloader-config.sh finished with exit code 100. Output: Get:1 file:/var/local/yolk ./ InRelease Ign:1 file:/var/local/yolk ./ InRelease Get:2 file:/var/local/yolk ./ Release [113 B] Get:2 file:/var/local/yolk ./ Release [113 B] Get:3 file:/var/local/yolk ./ Release.gpg Ign:3 file:/var/local/yolk ./ Release.gpg Get:4 file:/var/local/yolk ./ Translation-en Ign:4 file:/var/local/yolk ./ Translation-en Get:5 file:/var/local/yolk ./ Contents (deb) Ign:5 file:/var/local/yolk ./ Contents (deb) Get:6 file:/var/local/yolk ./ Contents (deb) Ign:6 file:/var/local/yolk ./ Contents (deb) Get:7 file:/var/local/yolk ./ Contents (deb) Ign:7 file:/var/local/yolk ./ Contents (deb) Get:4 file:/var/local/yolk ./ Translation-en Ign:4 file:/var/local/yolk ./ Translation-en Get:5 file:/var/local/yolk ./ Contents (deb) Ign:5 file:/var/local/yolk ./ Contents (deb) Get:6 file:/var/local/yolk ./ Contents (deb) Ign:6 file:/var/local/yolk ./ Contents (deb) Get:7 file:/var/local/yolk ./ Contents (deb) Ign:7 file:/var/local/yolk ./ Contents (deb) Get:4 file:/var/local/yolk ./ Translation-en Ign:4 file:/var/local/yolk ./ Translation-en Get:5 file:/var/local/yolk ./ Contents (deb) Ign:5 file:/var/local/yolk ./ Contents (deb) Get:6 file:/var/local/yolk ./ Contents (deb) Ign:6 file:/var/local/yolk ./ Contents (deb) Get:7 file:/var/local/yolk ./ Contents (deb) Ign:7 file:/var/local/yolk ./ Contents (deb) Get:4 file:/var/local/yolk ./ Translation-en Ign:4 file:/var/local/yolk ./ Translation-en Get:5 file:/var/local/yolk ./ Contents (deb) Ign:5 file:/var/local/yolk ./ Contents (deb) Get:6 file:/var/local/yolk ./ Contents (deb) Ign:6 file:/var/local/yolk ./ Contents (deb) Get:7 file:/var/local/yolk ./ Contents (deb) Ign:7 file:/var/local/yolk ./ Contents (deb) Get:4 file:/var/local/yolk ./ Translation-en Ign:4 file:/var/local/yolk ./ Translation-en Get:5 file:/var/local/yolk ./ Contents (deb) Ign:5 file:/var/local/yolk ./ Contents (deb) Get:6 file:/var/local/yolk ./ Contents (deb) Ign:6 file:/var/local/yolk ./ Contents (deb) Get:7 file:/var/local/yolk ./ Contents (deb) Ign:7 file:/var/local/yolk ./ Contents (deb) Get:4 file:/var/local/yolk ./ Translation-en Ign:4 file:/var/local/yolk ./ Translation-en Get:5 file:/var/local/yolk ./ Contents (deb) Ign:5 file:/var/local/yolk ./ Contents (deb) Get:6 file:/var/local/yolk ./ Contents (deb) Ign:6 file:/var/local/yolk ./ Contents (deb) Get:7 file:/var/local/yolk ./ Contents (deb) Ign:7 file:/var/local/yolk ./ Contents (deb) Get:4 file:/var/local/yolk ./ Translation-en Ign:4 file:/var/local/yolk ./ Translation-en Get:5 file:/var/local/yolk ./ Contents (deb) Ign:5 file:/var/local/yolk ./ Contents (deb) Get:6 file:/var/local/yolk ./ Contents (deb) Ign:6 file:/var/local/yolk ./ Contents (deb) Get:7 file:/var/local/yolk ./ Contents (deb) Ign:7 file:/var/local/yolk ./ Contents (deb) Reading package lists... W: No Hash entry in Release file /var/lib/apt/lists/var_local_yolk._Release Running bootloader-config...
Reading package lists... Building dependency tree... Reading state information... Package grub-efi-amd64 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: grub2-common grub-efi-amd64-bin grub-pc grub-common E: Package 'grub-efi-amd64' has no installation candidate Installing grub-efi-amd64 will get rid of the error, but a) it uninstalls MX Bootrepair which is needed for the workaround I have and b) the bootloader doesn't get installed anyway. FYI, the installation seems to work fine in a VM. It's just on actual hardware, the bootloader doesn't install. |
Beta Was this translation helpful? Give feedback.
-
|
Really interesting, I tried to boot your iso, it's OK unfortunately cannot log for the password... and mostly I have to go out, I'll take a look at it tonight. It might be: try to install |
Beta Was this translation helpful? Give feedback.
-
|
I'm currently uploading the ISO but in the meantime maybe there's something that could be wrong in here? BTW, I'm a total noob with Penguin-Eggs as well as configuring Calamares, honestly. :D |
Beta Was this translation helpful? Give feedback.
-
|
Here's the ISO https://drive.google.com/file/d/14DC5LMSlTJU9Jk2mRnNNPiAGRIsCN8L6/view?usp=sharing |
Beta Was this translation helpful? Give feedback.
-
|
I figured it out. I needed a partition.yml file in my wardrobe at modules/partition. I pulled the file from another wardrobe. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, forgot to mention the password. It's fearlessgeek, but I think I
figured it out. I have one more test I need to do which I will do today
…On Thu, Jan 11, 2024, 1:03 AM Piero Proietti ***@***.***> wrote:
Really interesting,
I tried to boot your iso, it's OK unfortunately cannot log for the
password... and mostly I have to go out, I'll take a look at it tonight.
It might be:
Package grub-efi-amd64 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
grub2-common grub-efi-amd64-bin grub-pc grub-common
E: Package 'grub-efi-amd64' has no installation candidate
try to install grub-efi-amd64-bin
—
Reply to this email directly, view it on GitHub
<#265 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3HGA5UVIJI5CXXIF3SSSEDYN56B3AVCNFSM6AAAAAA3SRJ352VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAOJQGQ3DE>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
OK, so the Grub installation works when I do a manual partitioning, but not the autoamtic partitioning/entire disk. It seems like it's not creating the /boot/efi. It only does it when I manually partition it. |
Beta Was this translation helpful? Give feedback.
-
|
I'm in the middle of uploading an updated ISO with changes I made yesterday. |
Beta Was this translation helpful? Give feedback.
-
|
Latest ISO - https://drive.google.com/file/d/12xhnNNcsrNtKoDUVWZRtiBOks2Y2IeCB/view?usp=sharing Hopefully it works anyway. I had several interruptions due to my current living situation and relying on the homeless shelter's wifi. |
Beta Was this translation helpful? Give feedback.
-
|
Well I tried another manual partitioning with a new ISO I created tonight and it failed to install the bootloader properly. So I don't know. Hopefully we can figure this out soon or I will need to switch to something else. |
Beta Was this translation helpful? Give feedback.
-
|
I've come to the conclusion that MX has made changes where it's best to work with MX Snapshot rather than use Penguin-Eggs with MX Linux. It seems thay've made some changes to Debian which break compatibility with Penguin-Eggs. It can work, BUT you have to run the MX Boot Repair after installation in order for Grub to install properly. Unfortunately, MX Linux does not allow me to have my own Grub theme when booting the live USB. It uses the MX Linux grub theme. Once installed, however, it uses my own Grub theme just fine. The MX Installer isn't as customizable unless I edit the code and recompile it. I noticed AV Linux didn't even bother to do that, however. They just created a Yad welcome app which launches the MX Installer. And I think that's going to be what I will resort to doing. Keep up the great work, though. I'd be interested in coming back to this if work is done to make this compatible with MX Linux. I may also make a Devuan-based ISO at some point. Does this work with Devuan? It's basically Debian but no systemd. |
Beta Was this translation helpful? Give feedback.
-
|
I think I'm too late to be helpful, but I'll give it a try on MX 23.1 to see what's what. I tried starting your ISO, but the password is not even what you wrote down! Never mind, I'll install MX and check So far I have simply installed MX 23.1, then removed: Now I am doing an Finished the upgrade, I removed the old kernels, then installed penguins-eggs. I used:
then:
At this point, because the latest version, currently 9.6.27 is not yet online, I updated it with my development version. To make sure everything was okay, I completely deleted the configuration by giving: At this point, I installed calamares atraverso eggs:
As I finish making the ISO I'll upload it to https://sourceforge.net/projects/penguins-eggs/files/ISOS/mx-linux/ and hopefully it will work and maybe help you. Right now I don't know either, because it's still building the ISO, I chose the --max compression option and it takes a while.
|
Beta Was this translation helpful? Give feedback.
-
|
Is loading the egg-of_mx-libretto-xfce_amd64_2024-01-14_0714.iso under mx-linux in the meantime I started the installation procedure with calamares. I didn't remember to enable autologin, anyway |
Beta Was this translation helpful? Give feedback.
-
|
It go nicelly...
|
Beta Was this translation helpful? Give feedback.
-
|
Creating the ISO isn't the problem. Does it actually boot on actual hardware? That's the problem I was having after installation on real hardware. It seemed that Grub didn't install properly, at least on my machine. I haven't tested the ISO you made on my machine as yes, you are a little late now and I've moved on from it. The thing was, it would install and boot properly in a VM, but when I actually tried to install the system on my laptop, it wouldn't boot up. That's the question I'm having. Is it installing Grub properly on real hardware? Because the installation it did for me did not install Grub properly. I have an HP Probook 440 G2 if that helps. I don't have an available drive to test it on right now, and currently broke so can't buy a new one. So I'm working with what I've got. So the problem isn't the creation of the ISO, or even getting to the finish screen. It's that, on my real hardware, it wouldn't boot into the drive I installed it too after installing. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I test just on VMs, can't literally test on real hardware, first becouse I have just my machine, second - and probably more important - I haven't time to do that. But as far as I know real users work with eggs, build ISOs and I suppose install it on VM and real hardware with more or less success. |
Beta Was this translation helpful? Give feedback.
-
|
Well testing on real hardware seems to me an important part of this. And I
can tell you with the ISOs I was building with Penguins-Eggs, it wasn't
installing Grub properly on real hardware.
I mean, I'm just here letting you know my experience on real hardware. So
yes, I did the testing for you there, at least with the ISOs I built with
it. So unless Penguins-Eggs is only meant to build ISOs for use in VMs
only, it might be a good idea to confirm it's working on real hardware or
fix it when it's not.
…On Sun, Jan 14, 2024 at 11:51 AM Piero Proietti ***@***.***> wrote:
OK,
I test just on VMs, can't literally test on real hardware, first becouse I
have just my machine, second - and probably more important - I haven't time
to do that.
But as far as I know real users work with eggs, build ISOs and I suppose
install it on VM and real hardware with more or less success.
—
Reply to this email directly, view it on GitHub
<#265 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3HGA5UTSUZCB4GGE7HRQTDYOQEJ5AVCNFSM6AAAAAA3SRJ352VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCMRUHEYTE>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
I understand you, but I can't test on specific hardware. I installed with eggs a lot of real computers, users probably tons. The rule of eggs is to let you replicate the system, add firmwares and so on is from your side, there are exceptions of course. Once the ISO is generated and the ISO install on a VM from eggs side is OK, find the reasons why the ISO not work on a specific computer not. From my side if have the right firmwares and so on it must work. |
Beta Was this translation helpful? Give feedback.
-
|
I have no problems installing other ISOs not made with eggs. I'm not sure it's a firmware issue. I'm not expecting you to test it on every piece of hardware. That would be unreasonable. OK, so you do test it on real hardware, because previously you said you only tested it on VMs. What firmware do I need to add to get it to install properly on my system? But then how am I supposed to make sure it installs properly on other systems using my ISO I made with Penguin Eggs? Why don't I need to install this firmware for other Linux distributions I install on my system? I'm sorry, but I kind of feel like Penguin Eggs isn't quite the tool for me. MX Snapshot works just fine. I wish I had more customization options with it, but it works. |
Beta Was this translation helpful? Give feedback.
-
|
Well, I am glad that mx-installer and mx-snapshot are working properly for you and I think you better use them on MX. This makes me think that, it's probably not a firmware problem since you're using the same ISO but the reason is something else. Which one, unfortunately I don't know. |
Beta Was this translation helpful? Give feedback.
-
This was also posted in "issues", and I wasn't sure if it should be there, or here in Q&A. Maybe another member can answer this question, so I also posted here. If the double-post is an issue, please remove whichever post is considered bad etiquette, and accept my apologies. With that said...
First and foremost...KUDOS on the PenguinsEggs project! As a former Remastersys and Systemback user, I have been searching for a viable replacement ever since they were both abandoned. The linux ecosystem DESPERATELY needs a tool to clone a currently existing installation to an ISO, for deployment of a homogeneous OS across a small network of computers. And Clonezilla is NOT that tool, for various reasons. I LOVE your PenguinsEggs project, which I have only recently discovered and have utilized to create a customized remix of my new favorite distro, to be deployed across my home network of computers, laptops, set-top boxes, etc...
I have downloaded the most recent DEB file from your page and installed to Debian 12 Bookworm. I have been able to use PenguinsEggs to successfully create the ISO, and have copied that ISO to USB for use as a Live-Media using dd. The Live-Media successfully boots in a VM, as well as actual computer hardware. Testing in VMs and hardwares has provided me with successful installations to UEFI/GPT systems, with no issues. But I have ONE machine with a BIOS that requires MBR partitioning that fails at the Calamares step of removing grub-efi and installing grub-pc. I have tried creating ISO with Calamares using "eggs produce --calamares"; i have tried removing calamares and installing through Debian (12 Bookworm) repos and creating ISO with eggs dad. I have tried using the krill installer, which also fails (not sure if that matters, or if its a clue), but I'm really only interested in the Calamares installer, as this custom remix will also be an installation candidate for family & friends who use Linux, but lack the technical expertise to use Krill (seems like maybe I lack that expertise also?).
I'm not sure if I'm doing something wrong in the process, or if I've found a bug in the process. I note the YAML file for eggs references "make_efi=true". Could this be the source of issue with Calamares failing to install to a BIOS/MBR system? I have the calamares log from a "calamares -d" installation, with terminal messages available at the failure point, and it does fail at the same point each time (see attached text file).
Please advise how to install to a BIOS/MBR machine. If I'm doing something wrong in the process, please correct me. If I have found a bug, please fix. I am anxious to use PenguinsEggs to deploy my remix across ALL my machines, as well as family & friends. If this issue can be resolved, PenguinsEggs will be the PERFECT tool for that use-case scenario, so THANK YOU for this wonderful tool!
Calamares log
Beta Was this translation helpful? Give feedback.
All reactions