Thank you for the shellprocess configuration script that successfully installs the correct bootloader packages during installation depending on the presence of the /sys/firmware/efi directory. The Debian settings for Calamares should be doing this properly, but it was failing for me and a lot of other people. Your script functions well and I have included it in my EznixOS project, with credit to Peppermint. Thank you!
The latest Debian based Peppermint ISO appears to have solved this issue. I even used the shellprocess script within my EznixOS project to overcome this very issue. Thanks to the Peppermint team for implementing an elegant fix to the problem Debian should have had working all along.
Are you testing these ISOs in a VM or on hardware? When I test the Gnome ISO in Virtualbox, I need to set the video graphics adapter to VboxSVGA. Virtualbox's VMSVGA will cause the behavior you are seeing. The hardware I have is older Intel and Nvidia cards that use the Nouveau drivers and I do not see any problems booting the Gnome ISO on my hardware. Wayland works fine in my testing. Btw, I like your Nyarch spin. Thanks for using Ezarcher to help construct it. I really like what you have done with...
Are you testing these ISOs in a VM or on hardware? When I test the Gnome ISO in Virtualbox, I need to set the video graphics adapter to VboxSVGA. Virtualbox's VMSVGA will cause the behavior you are seeing. The hardware I have is older Intel and Nvidia cards that use the Nouveau drivers and I do not see any problems booting the Gnome ISO on my hardware. Wayland works fine in my testing. Btw, I like your Nyarch spin. Thanks for using Ezarcher to help construct it. I really like what you have done with...
Are you testing these ISOs in a VM or on hardware? When I test the Gnome ISO in Virtualbox, I need to set the video graphics adapter to VboxSVGA. Virtualbox's VMSVGA will cause the behavior you are seeing. The hardware I have is older Intel and Nvidia cards that use the Nouveau drivers and I do not see any problems booting the Gnome ISO on my hardware. Wayland works fine in my testing.
Hello. Great to see some movement on ALG! I will download soon and give it a run. Thanks!
Some dependencies of Calamares recently updated, like kpmcore and pybind11, among other KDE related things. You will need to recompile Calamares against the most current versions in order to get a working installer. I have a video: https://youtu.be/3UUxHlRa8js describing the need to rebuild Calamares when it stops working.
If you are still puzzled by this, paccache is a program that comes with the pacman-contrib package. If you install pacman-contrib, paccache will work and so should the hook.
I had thought of removing that package about a month ago when Arch dropped the r8168 package for the standard kernel. Maybe it's time?
Must have been a temporary Sourceforge issue. I could not download any other Sourceforge host project since late last night. Now it appears to be working. There was nothing I could have done. :-)
Maybe a possible problem with the settings in the calamares-settings-debian package? I don't know. You can try contacting the maintainer of that package in the Debian repositories to see if any further testing can be done.
Since it is impossible to know every change you made to the packages I include or any changes to the build script you might have made, I do not have another theory. Sorry.
Did you have a chance to test my theory of the missing apt-transport-https package in your build? Any luck getting your respin to work?
The error code 100 points to possible network issues. Does your virtual machine have networking enabled and working? On another note, your screenshots have a completely different theme than the one used in my ISO, and there is no Debug button in the lower corner of the progress column near the About button. Your Calamares has none of my branding, is this even my ISO? If you are using my EznixOS project to build your own respin, please indicate that in your question. You may simply need to include...
The error code 100 points to possible network issues. Does your virtual machine have networking enabled and working? On another note, your screenshots have a completely different theme than the one used in my ISO, and there is no Debug button in the lower corner of the progress column near the About button. Your Calamares has none of my branding, is this even my ISO?
You can run Calamares from the terminal with: sudo calamares -d In order to have the debug output in the terminal window whiles Calamares runs and get more information about what is happening around the time of the error. EDIT: qt6 packages just updated, so Calamares will need a rebuild again. The archiso and mkinitcpio-archiso packages just updated, so lots of small changes are needed in profiledef.sh and the efiboot and syslinux folders too. The grub.cfg also needs some adjustments. There are lots...
You can run Calamares from the terminal with: sudo calamares -d In order to have the debug output in the terminal window whiles Calamares runs and get more information about what is happening around the time of the error. EDIT: qt6 packages just updated, so Calamares will need a rebuild again. The archiso and mkinitcpio-archiso packages just updated, so lots of small changes are needed in profiledef.sh and the efiboot and syslinux folders too. There are lots of little adjustments to make before new...
You can run Calamares from the terminal with: sudo calamares -d In order to have the debug output in the terminal window whiles Calamares runs and get more information about what is happening around the time of the error. EDIT: qt6 packages just updated, so Calamares will need a rebuild again. The archiso and mkinitcpio-archiso packages just updated, so lots of small changes are needed in profile.sh and the efiboot and syslinux folders too. There are lots of little adjustments to make before new...
You can run Calamares from the terminal with: sudo calamares -d In order to have the debug output in the terminal window whiles Calamares runs and get more information about what is happening around the time of the error.
I have never seen that particular error in my testing. Are you trying to respin your own ISO?
You got me motivated to get new ISOs out. I just uploaded a new set. Calamares has been updated to version 3.3.5 and Plasma 6 is on the KDE ISO. The new version of Calamares took a bit of tweaking and testing with all the small changes necessary to the module configurations. Thanks.
I have not even tried Plasma 6. I was going to wait a week or two and let some of the dust settle before wandering into whatever mess KDE has in store for me.
Arcolinux probably does not include os-prober by default. I did not see it listed in the packages file on their github project. CachyOS does include os-prober, and I would guess Garuda does as well.
Yay is not installed, and you do not need an AUR helper to install xf86-video-intel as it is in the regular Arch repos. I do include trizen as the AUR helper, so you can use it out of the box, but not necessary for this driver.
I removed the xf86-video-intel package as it is ancient, unmaintained code that supports old Intel chipsets. It can cause issues and conflicts with newer versions of mesa and newer modesetting drivers for more modern Intel graphics. I am sorry that by dropping this package, your system is left out.
I tested the iso on my Dell Optiplex 9010 from 2014 as it has Intel built-in graphics, and it boots and runs successfully. Is your computer older than 2014? I have a Core 2 Duo machine in the closet that I have not used in about five years, but I have not tested it on something that old. Just curious. Thanks for the feedback so far! :-)
Sorry, I don't really know. I never tried to force install an older package while building with archiso.
Thank you for the explanation of the terms CI/CD and "continuous delivery." Now that I understand that CI/CD is a development model and does not really affect users, I can see the benefit of using the terminology. If the Peppermint components are being developed and pushed out via CI/CD pipelines, then that can be easily explained on the website. Using the term continuous delivery is very confusing to users who are unfamiliar with the development model and its implications, as I was uniformed. Thanks...
Are you giving the virtual machine enough hard drive space? Are you downloading the latest version, 20.07?
Are you giving the virtual machine enough hard drive space?
Thank you so much! I was getting around to the realization that I had to solve this during the Calamares install. I wasted too much time time trying to build the initramfs-linux.img inside the chroot by altering the linux.preset and mkinitcpio.conf with the customize-airootfs.sh - needless to say it was not working. I was just looking over Erik's Github site for how he solved the issue and it appears very similar to your solution. Thank you for laying out the how-to so I did not have to decipher...
Have you had any trouble getting Calamares to install a recent archiso build? Ever since the archiso 46.1 release I have not had any luck getting a Calamares installed archiso build to boot past the Loading Linux linux line after grub. I think I isolated it to the initramfs being named archiso.img and the Calamares installed system wanting it named initramfs-linux.img but I am having no luck getting a working build with anything other than the initramfs being named archiso.img. Any ideas?
I put a video up on PakOS: https://youtu.be/pj7Q9wrtLuo I hope you get some feedback and further help in your efforts. I wish you well.
I installed PakOS in Virtualbox and successfully used a usb flash drive the was automounted by PCManFM. Is that your script at work? As for Virtualbox guest additions in the ISO, is that what you mean? If so, the deb packages virtualbox-guest-utils, virtualbox-guest-dkms, and virtualbox-guest-x11 need to be included in the live build. The instructions are in the text file prepare-howto.txt: Download the three .deb files for getting the Virtualbox guest additions installed. virtualbox-guest-dkms virtualbox-guest-utils...
I am anxious to do a video on your project. Do you think it is a good time with the current release? If you are planning an update to address any of the issues you raised, I will hold off until you are ready. Thank you for your involvement and I look forward to hearing from you. :-)
I will get to it by the weekend. During the week it's a little tight for time. Thanks
I am using the ISO salientos-v2019.02-x86_64.iso I am having some trouble getting the system installed. The first two attempts at partitioing the drive, Calamares failed to create a parttion table and then failed to create partitions. The third attempt got through the installation with manual partitioning, but I could not login with the password I created. Has anyone else described these types of issues? Just curious. Thanks.
Thank you. I will await your new release and look forward to it. Tbh, I pointed you in the direction of the build tools, but it is you who has done all the work. PakOS is uniquely your own creation and a wonderful system.
I wanted to ask your permission before I do a video on your creation. I am very impressed with the full version and I would like to do a look at video and point people to your download. Is that ok?
PakOS looks great so far. I would add leafpad and nano for gui and cli text editing. System-wide firefox browser plugins go in /usr/lib/firefox/browser/extensions/. Also, a gui package manager would be handy - synaptic perhaps. You can remove hplip and simple-scan since you did not include any other printer utilities. Without foomatic-db and system-config-printer, the hplip software will not do much on its own. For a firewall, ufw is great but its command line. The gui is gufw which brings in almost...
Wonderful news. Thanks for the reply. I eagerly await your next release. I always wait until Ubuntu releases their first point release of an LTS before doing anything with it. July will be fun. :)
I have been looking over your Bodhibuilder script and I have used it many times on Xubuntu with great success. However, After installing Virtualbox, since it takes UID and GUID 999, leaves Bodhibuilder unable to function unless I take all the necessary steps to reassign the UID and GUID of Virtualbox. After looking at Pinguy Builder's script, I noticed that there is a section at line 229: #Changing caspers user-uid sed -i -e 's@user-uid [0-9]*@user-uid 990@' /usr/share/initramfs-tools/scripts/casper-bottom/*adduser...
I have been looking over your Bodhibuilder script and I have used it many times on Xubuntu with great success. However, After installing Virtualbox, since it takes UID and GUID 999, leaves Bodhibuilder unable to function unless I take all the necessary steps to reassign the UID and GUID of Virtualbox. After looking at Pinguy Builder's script, I noticed that there is a section at line 229: #Changing caspers user-uid sed -i -e 's@user-uid [0-9]*@user-uid 990@' /usr/share/initramfs-tools/scripts/casper-bottom/*adduser...
I have been looking over your Bodhibuilder script and I have used it many times on Xubuntu with great success. However, After installing Virtualbox, since it takes UID and GUID 999, leaves Bodhibuilder unable to function unless I take all the necessary steps to reassign the UID and GUID of Virtualbox. After looking at Pinguy Builder's script, I noticed that there is a section at line 229: #Changing caspers user-uid sed -i -e 's@user-uid [0-9]*@user-uid 990@' /usr/share/initramfs-tools/scripts/casper-bottom/*adduser...