-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade scripts failed and bricked a system #20
Comments
I believe I have also run into this problem (or something very similar) after running This is from a fresh flash of an SD card with the original Novena image, and then running each of the upgrade scripts in order. The version of I do not have a zImage file, but it looks like eEnv.txt is instructing something (uBoot?) to boot to the zImage.buster kernel. As a test, I moved eEnv.txt out of the way and renamed zImage.buster to zImage. This resulted in no output via HDMI and nothing output on the serial console. Next I tried moving the kernel and dtb files out of the way and putting the recovery images in their place and I was able to see the uboot messages, it started the kernel, and I was able to SSH in. I can keep this SD card around for a couple days in case it'd be helpful at troubleshooting what went wrong. Just let me know what to do and I can report back the results. |
Honestly I can't see myself fixing this but instead making a new SD card image for people. The effort for testing upgrades like this is extremely high :\ Edit: I'm very happy for other people to do this but when I last did this it was a nightmare of having to load old images to SD and run the scripts manually. Could you paste the uEnv.txt or ... eEnv.txt? Maybe I can see something obvious. Or yeah, upload the image. |
Testing upgrades is indeed very time consuming. Several hours for a full test. I'm willing to do the testing though. I figure we're going to have to figure out these issues one way or another and end-to-end testing seems like it'll get the most reliable results. I'd also be happy to help with making a new "factory" image, and/or do testing for that. If you are going to make a new image, please watch out for #34. I am doing further testing right now to try to find a solution that result in me being able to use X11 on at least Buster, if not Bullseye. |
So currently I don't have a Novna set up for testing. If you give me a week or so to clear up some stuff I'll be able to set things up and start development again and get back to this. :)
…On Wed, Nov 09, 2022 at 05:15:53PM -0800, anon8675309 wrote:
[uEnv.txt](https://github.com/novena-next/docs/files/9976297/uEnv.txt)
[zImage.buster.zip](https://github.com/novena-next/docs/files/9976306/zImage.buster.zip)
Testing upgrades is indeed very time consuming. Several hours for a full test. I'm willing to do the testing though. I figure we're going to have to figure out these issues one way or another and end-to-end testing seems like it'll get the most reliable results.
I'd also be happy to help with making a new "factory" image, and/or do testing for that. If you are going to make a new image, please watch out for #34. I am doing further testing right now to try to find a solution that result in me being able to use X11 on at least Buster, if not Bullseye.
--
Reply to this email directly or view it on GitHub:
#20 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
technomancy in IRC ran the upgrade scripts on an existing buster install.
The senoko script failed to run since i2c-get wasn't installed.
The kernel upgrade script removed the old zimage and added a new uEnv.txt before confirming the actual buster install worked.
It also could be that u-boot-tools wasn't installed so zImage.buster couldn't be made.
I've updated the scripts with a hack to install these unconditionally for now.
What actually needs to be done:
The text was updated successfully, but these errors were encountered: