You should never get a "logon loop" problem if you do one simple thing to preempt it.
I have told you multiple times but you seem to forget every install you do.
Yup. I don't remember you saying do a simple thing. Only complicated stuff which I have forgotten.
Tom M :)
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
By tomorrow I hope to have that added to my permanent collection of notes. I will try the fix tomorrow morning. And hopefully regain 500,000 Rac!
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
I just followed your directions during a delete disk/re-install of Ubuntu 20.
And all I got was "this lousy error message". :)
ubuntu@ubuntu:/$ sudo update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `/cow'.
So much for it being "foolproof". It was simple.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
I just followed your directions during a delete disk/re-install of Ubuntu 20.
And all I got was "this lousy error message". :)
ubuntu@ubuntu:/$ sudo update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `/cow'.
So much for it being "foolproof". It was simple.
Tom M
After reboot with 2 gpus installed was able to run the update-grub.
Have Ubuntu repo version of BOINC installed. "use_all_gpus" set. And 5 gpus to test running.
Both E@H and Universe at Home are currently processing. The gpus are single threading for the night.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
You have terrible luck with installs I guess. I have no response other than Ubuntu hates you.
I've never had that error before.
I had to look it up. It seems that you were installing a dual-boot system, correct?
Problem was you didn't have chroot permission to the boot directory where grub resides.
So not a simple fix and way beyond what a beginner would be expected to know and understand.
Sorry for leading you astray.
Wasn't a dual boot system. But way I exited the reboot script may be the issue.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Plus the mb which has connection lights lights for every slot is lighting up slots l am not plugged into.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Keith Myers wrote: You
)
Yup. I don't remember you saying do a simple thing. Only complicated stuff which I have forgotten.
Tom M :)
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
OK, one more time. Before
)
OK, one more time. Before you reboot the system after the installation tells you to reboot, edit the grub file and remove "quiet splash" from the kernel command line. Then update-grub.
One simple edit and the problem is solved. I don't know anything much simpler than a couple of delete keystrokes and an update-grub command in the Terminal.
Keith Myers wrote: OK, one
)
By tomorrow I hope to have that added to my permanent collection of notes. I will try the fix tomorrow morning. And hopefully regain 500,000 Rac!
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Keith Myers wrote: OK, one
)
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Tom M wrote: Keith Myers
)
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
You have terrible luck with
)
You have terrible luck with installs I guess. I have no response other than Ubuntu hates you.
I've never had that error before.
I had to look it up. It seems that you were installing a dual-boot system, correct?
Problem was you didn't have chroot permission to the boot directory where grub resides.
So not a simple fix and way beyond what a beginner would be expected to know and understand.
Sorry for leading you astray.
Happy you were able to get
)
Happy you were able to get around the issue.
Keith Myers wrote: You have
)
Wasn't a dual boot system. But way I exited the reboot script may be the issue.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Could be. If you did anything
)
Could be. If you did anything other than dismiss the notification that the system will reboot now could have been the problem.
That is all I do. Dismiss the notification and then open a Terminal to edit the /etc/default/grub script to remove the quiet splash and save the file.
Then do a update-grub. Then I exit the desktop with a restart.
And all is well.
Plus the mb which has
)
Plus the mb which has connection lights lights for every slot is lighting up slots l am not plugged into.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!