Running into a weird issue here. I am trying to install Peppermint with the latest 64-bit May 2022 image. I created my boot USB with Rufus and it boots to the live environment fine. I can connect the Internet and work in the live environment. The live environment is stable.
Whenever I get to the user account creation screen, if I type any text into the "What is your name?" field (a single letter), the installer closes. I have tried filling out the login name, computer name, and passwords first and then going back to the name field, but that closes the installer too. I have also tried typing my name in the login field, then copying and pasting my name back into the name field with the same result... Calamares closes. It just does not like text in the field (for me, anyway).
For reference, my hardware is an old Asus 1015E netbook, Intel Celeron 847U, 2GB, that I upgraded with a 128GB SSD and an Intel 7260ac card. This laptop was previously running Peppermint 10 64-bit just fine (it shipped with Ubuntu way back in the day, 12.04 if memory serves me right). For partitioning, I am doing an "Erase everything" + swap with hibernate support (to get a larger swap of 4GB). Nothing fancy, just doing the defaults really.
Internet searches have not turned up anything for me yet on this one. Does anyone have an idea where I should look to get past this Calamares screen? Is there an alternate installer?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When this happens , have you installed any software into the live session , to try it out or made any changes in the desktop or the system before starting the installation ?
Or did you boot up the laptop and start the install from a fresh system ?
And if it is doing it at the same point every time it might be a corrupted download.
This is the first thing to check.
either verify the sha512sums with the checkfile here of SF with that ISO or get a fresh copy to try.
Thanks,
KsWoodsMan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did verified the SHA512 with the ISO prior to writing to USB and it passed, and I had not installed anything in the live session. I was just connecting to Wi-Fi and launching the installer.
SOLUTION:
I tried the fresh copy route. I re-downloaded the ISO, verified SHA512 again, and wrote the ISO again with Rufus (same as I process I used before).
This second version is working. So, it does indeed look like either the first download was no good (despite passing its checksum) or the first USB flash did not write correctly.
Either way, thank you for pointing me in the right direction.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@revove , You are welcome.
I'm glad it turned out to be an easy solution.
Welcome to Peppermint !!!
That sha512sum , it's reliable.
I can flip one bit in an ISO and the checksum will fail.
When I flip that bit back , it is good again and will pass the check.
A "bad burn" can happen just like a bad download can happen.
I've had a USB flash drive start to develop "unreliable sectors" before.
Usually the controller will catch these before they show up as errors.
But it had a lot of "miles" on it.
That's all "water under the bridge" now. Enjoy the Ride !
Thanks,
KsWoodsMan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Running into a weird issue here. I am trying to install Peppermint with the latest 64-bit May 2022 image. I created my boot USB with Rufus and it boots to the live environment fine. I can connect the Internet and work in the live environment. The live environment is stable.
Whenever I get to the user account creation screen, if I type any text into the "What is your name?" field (a single letter), the installer closes. I have tried filling out the login name, computer name, and passwords first and then going back to the name field, but that closes the installer too. I have also tried typing my name in the login field, then copying and pasting my name back into the name field with the same result... Calamares closes. It just does not like text in the field (for me, anyway).
For reference, my hardware is an old Asus 1015E netbook, Intel Celeron 847U, 2GB, that I upgraded with a 128GB SSD and an Intel 7260ac card. This laptop was previously running Peppermint 10 64-bit just fine (it shipped with Ubuntu way back in the day, 12.04 if memory serves me right). For partitioning, I am doing an "Erase everything" + swap with hibernate support (to get a larger swap of 4GB). Nothing fancy, just doing the defaults really.
Internet searches have not turned up anything for me yet on this one. Does anyone have an idea where I should look to get past this Calamares screen? Is there an alternate installer?
When this happens , have you installed any software into the live session , to try it out or made any changes in the desktop or the system before starting the installation ?
Or did you boot up the laptop and start the install from a fresh system ?
And if it is doing it at the same point every time it might be a corrupted download.
This is the first thing to check.
either verify the sha512sums with the checkfile here of SF with that ISO or get a fresh copy to try.
Thanks,
KsWoodsMan
I did verified the SHA512 with the ISO prior to writing to USB and it passed, and I had not installed anything in the live session. I was just connecting to Wi-Fi and launching the installer.
SOLUTION:
I tried the fresh copy route. I re-downloaded the ISO, verified SHA512 again, and wrote the ISO again with Rufus (same as I process I used before).
This second version is working. So, it does indeed look like either the first download was no good (despite passing its checksum) or the first USB flash did not write correctly.
Either way, thank you for pointing me in the right direction.
@revove , You are welcome.
I'm glad it turned out to be an easy solution.
Welcome to Peppermint !!!
That sha512sum , it's reliable.
I can flip one bit in an ISO and the checksum will fail.
When I flip that bit back , it is good again and will pass the check.
A "bad burn" can happen just like a bad download can happen.
I've had a USB flash drive start to develop "unreliable sectors" before.
Usually the controller will catch these before they show up as errors.
But it had a lot of "miles" on it.
That's all "water under the bridge" now.
Enjoy the Ride !
Thanks,
KsWoodsMan