Closed karasu closed 10 years ago
I'm also not sure about the locale error. There is not enough of the log to determine what it could be. It was the swap error that caused the hang up though so you should be able to complete it next time. Cheers!
im stuck at "configuring system startup" also when creating a new GPT table i get the bios-gpt message and it makes the bios gap partition. but i know i booted into uefi because in the terminal it lists the efivars just fine.
also i got multiple errors so i jst copied the full log
Wow, there's something very wrong here: WARNING: Command '['blkid', '-o', 'value', '-s', 'TYPE', '/dev/sda-1'] I think parted uses that sda-1 naming. I'll check it.
Also this is wrong: self.chroot(["%s", "&&", "/usr/bin/mkinitcpio", "-p", self.kernel_pkg] % export) I'll also fix it.
Thanks @fpsgamer101 !
Also this is wrong: self.chroot(["%s", "&&", "/usr/bin/mkinitcpio", "-p", self.kernel_pkg] % export)
oops :-/ I completely forgot to go back and fix this, sorry..
@fpsgamer101 Thanks for sticking with us through this testing. We know that there are some issues with GPT but for now, what I would like to do is focus UEFI testing on installation using regular MBR partitions. Once testing shows we are successfully completing UEFI installs for both automatic and advanced mode, then I want to shift our focus to GPT. If we focus on too many things at one time, progress will be slow (I don't like slow lol). Thanks for all of your help! ;-)
@karasu i already told you about the errors during partitioning before. those have been around for a while now.....
EDIT: @lots0logs i think i missed that memo. i have not read anywhere that you wanted to test MBR instead of GPT for now. but i dont mind. i just like helping. and since my python skills only go up to moving a turtle this is all i can do for now:)
i have not read anywhere that you wanted to test MBR instead of GPT for now.
I know because I just decided that would be the best thing to do 45 minutes ago hehe ;-) ..Seriously we appreciate the help!
@fpsgamer101 Sorry, I didn't read it. Now it's fixed in Antergos/Cnchi testing branch. As we can't test it ourselves your tests are very important to us. Thanks a lot.
EDIT: @fpsgamer101, if your're willing to learn Python, by all means, ask me all the questions/issues you find in the process. I'll be more than glad to help.
Now it's fixed in Antergos/Cnchi testing branch.
We try to keep Antergos/Cnchi and lots0logs/Cnchi in sync at all times. With myself and @karasu both keeping an eye on this there shouldn't be any issues where you would need to worry about which branch you are using. (At least that's our goal) We both have access to update the testing.sh script as needed so if you just remember to use the script everything should go smoothly :-D
ok i used mbr.
i had to create a small /boot partition infront of th root partition to be able to continue(i dont know if thats normal. probably though because of mbr space needed i dont know much about mbr sadly)
i got stuck at configuring startup again.
log: https://gist.github.com/fpsgamer101/7976801
p.s. @karasu thanks for offering you help i appreciate it. can you tell me if this is any good?: http://openbookproject.net/thinkcs/python/english3e/index.html and do you know any other good py3 lessons?
Alright, I've corrected the two errors that held you up this time. Thanks for those! For UEFI systems /boot must be on its own partition and formatted with fat32. It will be your UEFI partition. If you already have an existing UEFI partition you can mount it at /boot instead and you do NOT have to format it.
Cheers!
@fpsgamer101 : Check this out (it's the official tutorial) : http://docs.python.org/release/3.3.3/tutorial/index.html
If you already know another programming language you can go directly here: http://docs.python.org/release/3.3.3/tutorial/controlflow.html
Cheers!
@lots0logs wait.. but i made the drive mbr, you need uefi for that????????
@karasu haha ok guess i missed it great thanks.
@fpsgamer101 : You're welcome. By the way, I think you're mistaken about UEFI. Think like BIOS/UEFI, GPT/MBR
"GUID Partition Table (GPT) is a standard for the layout of the partition table on a physical hard disk, using globally unique identifiers (GUID). Although it forms a part of the Unified Extensible Firmware Interface (UEFI) standard (Unified EFI Forum proposed replacement for the PC BIOS), it is also used on some BIOS systems because of the limitations of master boot record (MBR) partition tables, which use 32 bits for storing logical block addresses (LBA) and size information."
So GPT is defined in the UEFI standard, but you can use UEFI with MBR or even BIOS (the newest) with GPT.
Cheers!
@karasu makes sense. Thanks
@karasu I tried to run a test install before work today but it got held up with a parted exception (releated to sda-1/sda1 issue i think) I don't have anymore time to investigate but wanted to let you guys know so you dont try to test until we fix this. Here is the trace: https://gist.github.com/lots0logs/8587869
Cheers!
I introduced a new bug while I was trying to fix another one, sorry for this. It should be fixed now (I'm off to work, I'll test it later)
EDIT: I've tested it and works for me.
Success! install completed booted up an working.
but i noticed 2 things.
1 there are 4 boot options in grub
next to antergos and fallback there are
Arch Linux pkg-linux kernel
Arch Linux pkg-linux kernel (fallback initrams)
i dont know if these are supposed to be visible?
2 apparently something in the antergos hdd makes the UEFI think's there is a windows bootloader in there(which there is not)
i will leave the log here for review. (read it there are some extra errors in there, at least a couple lines under ==> Starting build: 3.12.8-1-ARCH )
1 there are 4 boot options in grub
next to antergos and fallback there are
Arch Linux pkg-linux kernel Arch Linux pkg-linux kernel (fallback initrams) i dont know if these are supposed to be visible?
This is a bug in upstream grub that should be fixed soon.
2 apparently something in the antergos hdd makes the UEFI think's there is a windows bootloader in there(which there is not)
This is intentional as a fallback. Because each manufacturer's firmware is different we cant be sure it will always work .I will put some more thought into this. Perhaps we can set a script to run on first boot that will remove the Windows loader entry since at that point we would know the boot was successful.
THANKS FOR THE REPORT! :)
i have noticed some graphical glitches also things like glxinfo does not work.
what amd driver are you putting in?(stable, dev or radeon(opensource))
We include the opensource drivers. Are you getting any errors with glxinfo? It works fine for me.
when i type it i n the terminal i get glxinfo is not even installed? i think it goes to the vesa drivers for some reason because on for example the settings menu when i scroll the screen inside the window starts overlaying itself.
think that old windows error screen that when you drag it its everywhere like a paint brush or something
glxinfo is a part of mesa so u should have it..try reinstalling mesa?
On Mon 06 Jan 2014 03:08:12 PM CST, fpsgamer101 wrote:
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.
— Reply to this email directly or view it on GitHub https://github.com/Antergos/Cnchi/issues/65#issuecomment-31687138.
About the glxinfo issue, maybe we could follow this discussion in another place? (forum?).
And about this issue, as it seems to work, I'll close it for now.
Thanks for all the tests!!!!!!
@karasu only UEFI/mbr is working i checked and UEFI/GPT is still broken
I'm planning to review all of the GPT related code very soon including Grub/UEFI. @karasu , The comment trail on this issue is ridiculously long after all the testing to get Grub working. Let's go ahead and close this issue. Going forward we should probably comment on the the newer commits as they are made and tested. If we reference the previous commit in our comments then it will keep everything linked without creating one huge comment trail like we have here currently. (Did that make any sense? lol) It will be easier to demonstrate than explain haha ;-) Cheers!
OK. Closing this one. Opened this: issue #112
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