Closed karasu closed 10 years ago
@fpsgamer101 you should try this version https://github.com/lots0logs/Cnchi/tree/testing
ok used that one.
now i get this https://gist.github.com/fpsgamer101/7976801
oops..looks like I was more tired than I thought last night b/c I gave you the wrong path to packages.xml file. Sorry! It is "sudo -E cnchi -dv -p /usr/share/cnchi/data/packages.xml"
ok, almost went through this time...iso 23.12. + Dustin's testing branch crashes at grub installation. this is what I remember from the log (couldn't copy it, cuz system crashed completely)
command '['grub-install --target=x86_64-efi --efi-directory=/install/boot/efi --bootloader-id=antergos_grub --boot-directory=/install/boot --recheck']' returned non-zero exit status 127
and then at the end CalledProcessError.ouput=None
Then the system crashed
Seems I made a booboo lol I beleive its corrected now :)
still getting stuk at downloading antergos-testing.db
used logs version after the fix. log: https://gist.github.com/fpsgamer101/7976801
also did someone look into the menu bug?
if you did not understand what i meant i meant the first menu after loading the usb.(the text based one)
position is al the way top left so its wierd.
Are you certain you used what's in my latest testing branch? The error you are getting is before I applied the fix for issue #92 I posted a script in the forum that automates the process of updating cnchi files to the latest from github. Just run it from within the live system after you exit the initial welcome screen. Be sure to use "sudo -E" to run it.
Regarding the menu, I understand the issue but it doesn't happen on my tests so I'll have to look into it further to find the cause.
Thanks for all the help testing! Hope everyone has a happy holiday!
EDIT: I guess this would be helpful lol http://forum.antergos.com/viewtopic.php?f=5&t=1285
guess you used the master branch?
merry christmas everybody!
new day, new test run...used the testing script for the first time. maybe you should add rsync. It hang cuz it couldn't find rsync. I installed it manually.
Install failed with the same error but I got a log this time. http://pastebin.com/06w4PUQS
@lots0logs i got the one from your branch directly from github so im sure cause at the time that fix was 15 hours ago
also i ran that one with the terminal in that folder and used ./ to make sure it was going to run that file.
@DaElsta There was some leftover code from before the changes we made to get UEFI working. The error you got was because grub package had not been selected and installed. That should not happen now. Also I change the setup script so that it shouldn't need rsync (temp solution). Thanks!!!
@fpsgamer101 Is it possible you downloaded my master branch instead of testing? DaElsta would not have gotten to the point in installation that he did if the bug that cause the error you posted was still present. I've updated the testing script so give it a try instead of downloading archive from github.com Here is the link: http://antergos.info/testing-setup.sh Use "sudo -E ./testing-setup.sh" to run it. Thanks for your help!
@lots0logs it was this one https://github.com/lots0logs/Cnchi/tree/testing
and because of the holidays i am stuk with my mbr laptop til i get back home so. ill try it as soon as possible
new try - rsync error is gone, but cnchi still crashes with the exact same error as yesterday (grub-install command not found etc.)
I'm not sure why cnchi is not recognizing your bootloader type. I will look into it further and consult with @karasu. In the meantime I am going to force install grub so that you can continue past that error and see if everything else works.
Ok, I've tested it successfully in VBOX with EFI boot! Hopefully you will have some good news this time :+1:
well the install completed.
but after reboot i get the grub terminal(not rescue i mean the default one) it cant seem to load the menu
i installed the os on a second drive with bootloader there to.
I have a pretty good idea at what's caused the grub menu issue. I will update once I have made the changes. Thanks!
Does your system already have an EFI partition or did you create one during install? If the EFI partition already exists, ensure you mount it at /boot/efi (in advanced mode). If you don't already have one, go ahead and create it and mount it at the same point (/boot/efi). If you do create one, it should use the vfat filesystem type and be no larger than 512MB. This is really difficult to troubleshoot without having any UEFI boot systems at our disposal. Thank both of you for your help in testing.
well here we go again.
got stuck at installing grub
i use a second drive for testing so i partition with a new gpt partition table the EFI partition is fat32 (since vfat is not really an option in gparted or cnchi plus fat32 is most commonly used) and its 101mb(so it shows up as 100) mounted at /boot/efi
I've rewritten the grub theme install but havent tested it yet. I'm hoping this will resolve the issue.I pushed commit to my testing branch.
ok now i get stuk at installing grub theme
Alright, I got it working in virtualbox finally but I'm more interested in finding out if its working on your systems! ;-)
almost but falling apart. got stuck at partitioning no /boot/EFI option (yes the drive is GPT) EDIT: forgot the log
Sorry I forgot to mention that EFI partition should be mounted at /boot instead of /boot/EFI. Doing it this way keeps the path to the bootloader the same as it is listed in the UEFI specifications (within a single directory named "EFI" on the fat32 partition). This will be made more clear to the user, I still need to polish it up a bit but it should be working.
well stuck at installing grub again.
I should have known better than to just throw in os-prober without testing it myself first. :-D i'll remove it until we figure out the reason its not working...sorry!
Edit: the testing setup script has been updated so use the new one. same link. THANKS.
ok i think we can rule out os-prober as the cause. because i got the exact same result and looking at the log it says something is breaking in the installation_process.py file cause i get this output right before it starts the grub installation.
installation_process.py - root - ERROR - Unknown Error
Yep I found the issue a few minutes ago. im running a test now to make sure its fixed.
Alright it is once again working in virtualbox with uefi :-)
well it it installs now so... PROGRESS the bad news is that it now gets stuck at the next part. here is the log. log: https://gist.github.com/fpsgamer101/7976801
Grrrr...I dont understand how it works on vbox and not on for your machine. UEFI is making my head hurt lol It looks like it may have completed everything, what happens when you try to boot?
EDIT: do you still have the log? Cnchi does more than one thing at a time so the log messages are not in exact order. The problem wont always be at the end so it helps to look further back...
@lots0logs the problem there is that there are no other errors just a hardware module error and an unknown one in the installation_process.py also vbox is not using the same uefi that is on actual hardware. its using oracles version of it which is built for virtualization and virtualization is never equal to hardware itself. just like mac has a different uefi than pc.
EDIT: just rememberd there where other errors but those are in the log in the partition post the /boot/efi one so you have to go a revision or two back with fs_module.py in it
Yes I realize there will be differences of course. I used the technique from the Arch Wiki for the current setup and that seems to not be working so I will poke around some other distros and see what they are doing ;-) ...so when you tried to reboot did you get any bootloader screen at all or just the shell?
yes i got the grub menu (no theme = black and white) with antergos options but no windows. also did not go past it because i thought t woulb break.
tomorrow with a little luck i should be home early so i will redo the install to see if i get any new errors in the log. and if not this time i will at least try to boot it.
I havent included os-prober just yet so thats why there was no windows in the menu. There should have been a theme though so that's something I'll take another look at. Let me know if it boots or not. THANKS!!
ok i dont know what you did but it got worse it wont even get to the grub install now it hangs at "configuring display manager" (even though the log says its at the boot loader)
il just leave the whole thing here for now log: https://gist.github.com/fpsgamer101/7976801
i believe i found the cause so I removed the offending line of code. also the testing.sh script has been updated. thanks!
still not getting past "lightdm: configuring dispaly manager"
Alright, I'll work on it and let you know when its ready to test. Thanks!
Alright, I finally found and fixed what was causing the hangup after display manager setup. Please test again when you have time and let me know the result. Thanks!
good news: it completed install.
bad news: it skipped grub install all together...
also i got a btrfs error, i am using ext4.
We've added some checks to verify whether or not grub is installed properly. Please bring me some good news this time! ;-)
i cant get to the partitioning
When i select advanced partitioning i get a blank window
Did you happen to keep the log from when this happened?
i forgot so i redid the install.
wierd it looks like it breaks when looking at my primary drive EFI system partition. but nothing changed there since last try(the install is always on my second drive including the bootloader)
Here it is: https://gist.github.com/fpsgamer101/7976801
I've got this issue corrected as of 10 minutes ago :-)
Hey guys, just to let you know. I'm pretty busy right now. Continue testing in February.
No worries!! :-)
another day, stuck with the same text(display manager)
also apparently it fails to set my locale?
Don't know about the locale error, but I've fixed the error about swap shown in the log. Let's wait for @lots0logs
UEFI setups need some love. Test that Cnchi works with UEFI+mbr and UEFI+ GPT
Edit: UEFI/MBR is working, UEFI/GPT is not. Follow new issue here: issue #112