Timeline for Kernel in use does not match headers after manual update
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12 at 0:36 | vote | accept | letmeinLetMeInLETM | ||
| Apr 11 at 18:11 | history | edited | letmeinLetMeInLETM | CC BY-SA 4.0 |
added 1669 characters in body
|
| Apr 11 at 9:56 | review | Close votes | |||
| May 2 at 3:03 | |||||
| Apr 11 at 1:21 | answer | added | Milliways | timeline score: 0 | |
| Apr 11 at 0:11 | comment | added | letmeinLetMeInLETM |
I've seen some point to hashes of old releases to revert. Would something like sudo rpi-update master c4617e02da233ff70940223a06e568a193fc446d work since it points to 6.1.21?
|
|
| Apr 10 at 22:46 | history | edited | letmeinLetMeInLETM | CC BY-SA 4.0 |
added 4 characters in body; edited title
|
| Apr 10 at 22:12 | comment | added | Milliways | NOTE the current OS now uses 6.6 kernel. You would need to use rpi- update to get 6.1 but this is complicated. | |
| Apr 10 at 22:05 | comment | added | Milliways | Lots of irresponsible people suggest rpi-update but the program itself WARNS you not to use it. Why did you ignore the warning? DO NOT use apt-get use apt. The restoration commands have changed for recent OS. Restore from your backup. | |
| Apr 10 at 22:00 | comment | added | Dougie |
Run sudo apt install raspberrypi-kernel raspberrypi-bootloader to undo the damage you've done with rpi-update
|
|
| S Apr 10 at 20:03 | review | First questions | |||
| Apr 10 at 22:00 | |||||
| S Apr 10 at 20:03 | history | asked | letmeinLetMeInLETM | CC BY-SA 4.0 |