Any new on how made this steps / solved this issue?

I search for internet, but I don't view how made this steps exactly / fixed this issue.

I have a computer that, I can't shutdown or restart :-P

Regards!

Not saying this is the correct way but when my new install from usb failed what I did was -

Rebooted but changed it so that it booted from the usb.
Opened Neon to "try it" and then opened a console.

Entered those commands exactly as shown - where 'sudo' requires root password I used the one entered when I installed the system.

Exit usb version of Neon, reboot and hopefully a reboot will bring up the installed Neon as it did for me.

(I didn't have a rescue disc or similar, might set one up now)

Jim

Ok, thanks Jim, I was need that you indicate now, how you made this steps.

After a 2 or 3 hours, go to made this and test.

Also, I don't have rescue disck, I try with boot repair, but not work).

Regards!

I see that a new iso snapshot (23112017) has been published today. Has anyone tried this? Is the grub issue fixed?

I have tried the latest iso snapshot and this has the same grub issue.

Is it just me or is it pretty bad to publish a new iso when the grub issue is unresolved?

I have just tried the latest iso and can confirm it is not just you, same thing happening here.

I ended up downloading an earlier snapshot from Distrowatch torrent archive and it has installed and booted ok.
https://distrowatch.com/dwres.php?resource=bittorrent

gfielding wrote:I see that a new iso snapshot (23112017) has been published today. Has anyone tried this? Is the grub issue fixed?

Thanks for you reply

jamesp1968 wrote:I have just tried the latest iso and can confirm it is not just you, same thing happening here.

I ended up downloading an earlier snapshot from Distrowatch torrent archive and it has installed and booted ok.
https://distrowatch.com/dwres.php?resource=bittorrent

Thanks for indicate this link!

gfielding wrote:I see that a new iso snapshot (23112017) has been published today. Has anyone tried this? Is the grub issue fixed?

Hi there,

I still have exactly the same issue with KDE Neon iso snapshot 23112017 (download from here https://files.kde.org/neon/images/neon- ... -amd64.iso). I'm wondering if reinstalling with the lts edition would stay away from this issue.

Btw, does anyone know what is the difference between neon-useredition-20171123-1018-amd64.iso vs. neon-useredition-current.iso in here https://files.kde.org/neon/images/neon- ... n/current/

Both ISO's suffer from the same issue.

The items on the download page are:

neon-useredition-20171123-1018-amd64.iso Live and Installable ISO
neon-useredition-20171123-1018-amd64.iso.sig PGP Digital Signature
neon-useredition-20171123-1018-amd64.manifest ISO contents
neon-useredition-20171123-1018-amd64.sha256sum Checksum
"current" files are the same files for those wanting a URL which does not change daily.

tungtanium wrote:

gfielding wrote:Btw, does anyone know what is the difference between neon-useredition-20171123-1018-amd64.iso vs. neon-useredition-current.iso in here https://files.kde.org/neon/images/neon- ... n/current/

The current iso is whatever the latest daily image is

Btw, does anyone know what is the difference between neon-useredition-20171123-1018-amd64.iso vs. neon-useredition-current.iso

The two are the same thing.

gfielding wrote:Both ISO's suffer from the same issue.

The items on the download page are:

neon-useredition-20171123-1018-amd64.iso Live and Installable ISO
neon-useredition-20171123-1018-amd64.iso.sig PGP Digital Signature
neon-useredition-20171123-1018-amd64.manifest ISO contents
neon-useredition-20171123-1018-amd64.sha256sum Checksum
"current" files are the same files for those wanting a URL which does not change daily.

Those are instances of the same ISO, as indicated by the checksums. So those are not two ISOs but two identical instances of the same ISO. And you can create a thousand instances by copying or re-imaging.

Wykedengel wrote:

apachelogger wrote:The latest user edition ISO passed automatic quality control, so I doubt it's a problem with the ISO.

Had the same issues doing a fresh install on my Lenovo Thinkpad T440s. Had to be online to install, then booted up to a pretty grub prompt. Was able to address the issue using the tried and true:

Code: Select all

mkdir efi

Code: Select all

sudo mount /dev/sda 1 efi/

(or whatever your efi boot partition is called)

Code: Select all

sudo cp efi/EFI neon/* efi/EFI/ubuntu/

Then all was good.

This is my first time with KDE Neon. Talk about a rough start.

Hi Wykedengel,

So just run these commands straight from the mini-bash grub?

Regards,

claydoh wrote:

tungtanium wrote:

gfielding wrote:Btw, does anyone know what is the difference between neon-useredition-20171123-1018-amd64.iso vs. neon-useredition-current.iso in here https://files.kde.org/neon/images/neon- ... n/current/

The current iso is whatever the latest daily image is

Thank you claydoh.

There is another thing that I am wondering. Please excuse for my noob on KDE Neo (and Linux in general): Can I just use another working iso (snapshot 20171108) and re-install on the same partition of the broken one (snapshot 23112017)?

Regards,