Ubuntu

24.04 updates caused no start at reboot and grub no response to kb input

Asked by capt mckenzie

latwst Ubuntu installed as upgrade last week. No obvious problems. Notfied of standard updates by A icon. Accepted and updates appeared fine. Instructed to restrt and accepted. System frozen after grub screen. Only exit by forced machine shutdown to restrt. Same result three times so tried to use grub to select dual boot win11. kb input of down arrow not recognised. Tried to E for edit - no response and system moved on to boot then fails as before.
I am completely screwed at this point!
stuart mckenzie

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
capt mckenzie
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

If you boot an older kernel, is it OK?

Revision history for this message
capt mckenzie (demo-6) said : 		#2

How can I access an older kernel?? As grub not responding I cannot select advanced ubuntu or anything else. Perhaps through the machine interface?
jsm

Revision history for this message
capt mckenzie (demo-6) said : 		#3

Additional. This is an AMD threadripper 2995 with 32cpu/64 thread
jsm

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#4

Hold SHIFT at boot, you will see GRUB. You can then use cursor keys and ENTER to navigate the menu

Revision history for this message
Manfred Hampl (m-hampl) said : 		#5

Is this a Laptop with built-in keyboard or a desktop with a separate keyboard?
Does the keyboard work in the very first steps of the boot process where you have to press a certain key to enter BIOS setup?
Have you tried a different keyboard?

Revision history for this message
capt mckenzie (demo-6) said : 		#6

answering latest
yes the kb works with F2 to enter BIOS UEFI
It is a large tower threadripper
no need to change kb as works with F2 and also was working fine right up to when I accepted the instruction to restart. It also works on three other computers

now used uefi to boot windows to prove hardware OK. win11 running fine please suggest how I move on from here using uefi
it is late here so going to bed but will be back in a few hours (0600 local time Isle of Man)

Revision history for this message
capt mckenzie (demo-6) said : 		#7

back working ready to try suggestions

Revision history for this message
capt mckenzie (demo-6) said : 		#8

update:
Followed advice to hold shift down while booting. Excellent advice this worked.
Not sure of procedure from this point but grub available so chose advanved ubuntu: second entry down to boot: recovery mode: updated grub: continue normal boot
Result is login screen and now running. However I dont know at this point what kernel running but will leave for a bit to confirm current position and then restart to assess where we are.

Revision history for this message
capt mckenzie (demo-6) said : 		#9

I suspect this problem is video driver related because I saw the updates which caused this freeze deleted nvidia files. Perhaps I need to get into grub and add nosplash???
jsm

Revision history for this message
capt mckenzie (demo-6) said : 		#10

update:
after running OK for an hour out of recovery mode tried restart with editing quiet splash to nosplash. NBG same freeze but nothing on screen.
so now back to recovery mode with second boot line engaged from advanced ubuntu. This is running all software fine.
Plesae help me recover the 'updated' image and resolve what canonical has done to cause this problem
jsm

Revision history for this message
capt mckenzie (demo-6) said : 		#11

Do ubuntu support read these comments? This update is evidently a serious bug however it was caused.
jsm

Revision history for this message
capt mckenzie (demo-6) said : 		#12

Asked copilot for suggestions and AI said to use nomodeset in locl edit of grub. Did so and hey presto - success. Howevver the advice waas to edit grub default with nano and set the default linux string to null. This did not work but setting it to nomodeset and saving did the trick. I hope this helps others in the same boat.
I wish canonical would address this nvidia driver problem!
capt McKenzie