Mickynuts Posted Tuesday at 11:54 AM Share Posted Tuesday at 11:54 AM (edited) Hello, sorry for the tag (no odroid m1 tag) and if I'm in the wrong place. I downloaded the image Armbian_24.8.3_ordoidm1_jammy_current_6.6.51_kde-neon-kisak-desktop The image does not start without pressing rcy, so far normal. After flashing the mtd with armbian-installer and copying to SSD. The image still does not start. No display. After trying several things and without success, I decided to try an old image: Armbian_24.2.1_ordoidm1_jammy_current_6.6.16_xfce_desktop. I here rcy boot, install, copy to SSD, flash mtd and reboot. And it works. So I tried image 6.6.51 kde Again. But without flashing the mtd. And there it boots without problems and no need for rcy. So it seems that the last image and also the 24.2. 4 that I tried. We have a probably corrupted uboot. I have the odroid m1 8gb. I hope this will allow others not to waste hours trying because of a corrupted uboot. (This was my first attempt with armbian on this card. Before I had petitboot.) Sorry for my bad English. I used Google translate. PS: I tried to make a bug report form. But you have to provide an armbianmonitor -u output or something like that. And that doesn't match the fact. The card doesn't even boot. Edited Tuesday at 11:55 AM by Mickynuts 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted Tuesday at 12:50 PM Share Posted Tuesday at 12:50 PM moved 0 Quote Link to comment Share on other sites More sharing options...
usual user Posted Tuesday at 06:32 PM Share Posted Tuesday at 06:32 PM 6 hours ago, Mickynuts said: I tried to make a bug report form. But you have to provide an armbianmonitor -u output or something like that. And that doesn't match the fact. The card doesn't even boot. To get help, you have to provide proper logs. In case of boot problems, these are serial console logs. https://debug.armbian.de 0 Quote Link to comment Share on other sites More sharing options...
Mickynuts Posted Tuesday at 07:06 PM Author Share Posted Tuesday at 07:06 PM 29 minutes ago, usual user said: To get help, you have to provide proper logs. In case of boot problems, these are serial console logs. I don't need help anymore. As said. I used the uboot present in an earlier version. I didn't try the serial, because there weren't even any screens (I thought there wouldn't be a serial either). The card seemed to just do a reboot Every 5 seconds (depending on the LEDs on the network card and the LEDs on the SSD which flash 1x. I'm not going to try again now that I have a working installation. I just wanted to share with you Other beginners who are not used to this kind of tools and not have the serial cable. 0 Quote Link to comment Share on other sites More sharing options...
usual user Posted Tuesday at 07:54 PM Share Posted Tuesday at 07:54 PM 46 minutes ago, Mickynuts said: I don't need help anymore. As said. I used the uboot present in an earlier version. Ok, then no further action needs to be taken and your solution can be used by others in the future. I also don't need any other firmware because my current one works according to my needs. And for an update, I know how to build and debug it if necessary. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.