Can't boot anymore after upgrading bios to 1.22

Post Reply
baz
Posts: 3
Joined: Wed Feb 10, 2021 10:58 pm
languages_spoken: english
ODROIDs: h2+
Has thanked: 0
Been thanked: 0
Contact:

Can't boot anymore after upgrading bios to 1.22

Post by baz »

I received 3 H2+ boards with 1.12 bios. I use Kingston KVR24S17D8/16 (it is not in the list of compatible). I have booted live usb and everything was fine. Then I upgraded bios to 1.22 and can't boot anymore.
If no bootable options is left it boots to bios setup just fine. If I put any bootable drive or enable PXE, it will either show black screen or American Megatrends logo. If I press power button (without holding) it will shut off immediately.
Worst thing is I can't downgrade bios, because to do it, I have to boot of usb stick (and it doesn't work). Same behavior on all 3 boards (I have tested one and then upgraded all 3).

misaz
Posts: 85
Joined: Sat Jul 27, 2019 3:58 am
languages_spoken: english, czech
ODROIDs: H2+
Has thanked: 7 times
Been thanked: 15 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by misaz »

Did you reset BIOS settings to default after flashing BIOS?

baz
Posts: 3
Joined: Wed Feb 10, 2021 10:58 pm
languages_spoken: english
ODROIDs: h2+
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by baz »

misaz wrote:
Wed Feb 10, 2021 11:11 pm
Did you reset BIOS settings to default after flashing BIOS?
Yes

baz
Posts: 3
Joined: Wed Feb 10, 2021 10:58 pm
languages_spoken: english
ODROIDs: h2+
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by baz »

Was trying just everything last 2 hours and one thing worked. Put usb stick, press del during boot to get to bios, in bios press save settings without changing anything (discard settings won't work) and after that it will boot usb stick.
Flashed 1.12 and everything went back to normal.

Shadow0
Posts: 4
Joined: Fri Feb 12, 2021 6:09 am
languages_spoken: english
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by Shadow0 »

Hi!
Also updated the BIOS to 1.22. Just like you do not see bootable devices.
Unfortunately, your method did not help, I can not enter the BIOS on the screen saver HARDKERNEL and that's it. There is no response to the del key.
Resetting BIOS settings (disconnecting the battery from the board), did not help.
What should I do now?

Shadow0
Posts: 4
Joined: Fri Feb 12, 2021 6:09 am
languages_spoken: english
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by Shadow0 »

I dropped the bios again, and was able to enter it. Bios sees flash drive and nvme, but the list of boot devices is empty.
IMG_20210212_111624.jpg
IMG_20210212_111624.jpg (379.71 KiB) Viewed 2854 times
IMG_20210212_111635.jpg
IMG_20210212_111635.jpg (351.05 KiB) Viewed 2854 times
IMG_20210212_111811.jpg
IMG_20210212_111811.jpg (280.42 KiB) Viewed 2854 times

Shadow0
Posts: 4
Joined: Fri Feb 12, 2021 6:09 am
languages_spoken: english
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by Shadow0 »

The board stood overnight without a battery. A flash drive appeared in the BIOS. I flashed the BIOS for version 1.12.
Bottom line: the BIOS always sees the USB flash drive, but nvme and hdd do not appear in the boot devices.
But if I go to the menu Security -> Secure Boot -> Key Management -> Enroll Efi Image, then I can see the nvme boot partition and the files on it.
Why does the BIOS not show nvme and hdd in Boot Option?

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

Please, help!
I stuck with the same problem.
I bought H2+ on December. I received the board with BIOS v 1.12.
The used RAM: AMD Radeon R748G2400S2S-U, 2x8=16GiB totally.
All was working fine, I tested Fedora 33, Manjaro and finally installed CentOS 8 for further usage.
Unfortunately yesterday I decided to upgrade BIOS to latest 1.22. The upgrade procedure passed fine.
During first reboot I entered to the BIOS and performed "Restore Defaults".
And after that I can't boot anymore.
I tried to boot from SATA SSD with installed CentOS 8.
I tried to boot via BIOS from the same USB storage device I used for BIOS update.
I tried to downgrade BIOS running UEFI from several USB sticks with previous BIOS versions, but it can't boot as well.
I tried the same with disconnected battery and after motherboard was left without power for more than 10 minutes.
Nothing helps to boot in any variant, I can only enter to BIOS, select device to boot from, and after I press enter, just black screen is shown and all hangs.
Both blue and red LEDs light and do not blink.
Short press on Power button just switches off the motherboard instantly.
Any idea how to restore good state of my H2+ is highly appreciated.

User avatar
odroid
Site Admin
Posts: 38159
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2045 times
Been thanked: 1221 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by odroid »

We will receive another problematic DRAM modules(G.Skill F4-2400C16D-16GRS 8Gx2) with BIOS 1.22 a couple of weeks later.
And we will try fixing the DRAM compatibility problem.

Meanwhile, try downgrading the BIOS to v1.12 as this user did.
viewtopic.php?p=319588#p319588
If it doesn't help, try disconnecting the BIOS backup battery several minutes without DC plug to reset any possible wrong settings just in case.

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

Thank you for your help, odroid.
odroid wrote:
Tue Feb 16, 2021 11:25 am
Meanwhile, try downgrading the BIOS to v1.12 as this user did.
It was one of the first things I performed yesterday.
odroid wrote:
Tue Feb 16, 2021 11:25 am
If it doesn't help, try disconnecting the BIOS backup battery several minutes without DC plug to reset any possible wrong settings just in case.
I wrote, that yesterday I already did so.
Even more, all last night motherboard spent with disconnected battery and PSU.
Today I repeated the try.
I used old flash stick formatted to FAT32 (esp flag is set on partition just in case) with unzipped content of that v1.12 BIOS archive.
The problem is that when BIOS started to boot from any drive it just hangs.
Let me show it on the following photos. BTW do you have a list with POST codes and their meaning?

1. 1st enter to BIOS after MB laid w/o power and w/o battery. No any settings were changes in the BIOS.
Image
Image
Image
Image
After "Enter" was pressed on the last screen, the only black screen appeared and no other progress happened.
The keyboard lost control, the LED on the USB flash drive stopped to blink.
I had to press reset button.

2. 2nd enter to the BIOS.
Now I disabled Quiet Boot:
Image
Image
Now we can see some texts during boot before the process hang:
Image
And finally we can see some code 99. I suppose it's a POST code, isn't it?
Image

I created a short video of boot process, where more POST codes were shown before final 99:
https://drive.google.com/file/d/1my37Ru ... sp=sharing

Hence I can't burn the older and any other BIOS version.
And I can't boot from any device I tried anymore.
Do you have some ideas how this issue could be fixed?
May be is it possible to flash older BIOS version via serial console? I need instructions for that :)
Or could you advice some "more right" BIOS settings?
Should I check something else in the BIOS?

User avatar
odroid
Site Admin
Posts: 38159
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2045 times
Been thanked: 1221 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by odroid »

We couldn't reproduce the issue and it is hard to find what's different in the BIOS settings.

Can you try booting from a USB storage as @defcon did?
viewtopic.php?p=321669#p321669

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

odroid wrote:
Wed Feb 17, 2021 11:18 am
We couldn't reproduce the issue and it is hard to find what's different in the BIOS settings.
You know, I am software developer and work at PC more than 27 years.
A lot of PCs I assembled during this period.
And with H2+ I got a trouble after BIOS upgrade first time in my life.
It's despite the fact that I used RAM listed in your compatibility list as officially supported.
I can't express how much I am upset.
odroid wrote:
Wed Feb 17, 2021 11:18 am
Can you try booting from a USB storage as @defcon did?
viewtopic.php?p=321669#p321669
Thank you for the pointer, I tried to boot Ubuntu 20.10. It doesn't work, just hangs.

Why do you just ignore details I wrote you in my previous messages?
I tried to boot from USB storage (3 different USB devices), from SATA storage (SSD and HDD).
All those devices worked perfectly on H2+ with BIOS v1.12.
But after I upgraded to v.1.22 I can't boot from any storage! So I can't downgrade the BIOS.
Sorry, I have to repeat it again: any attempt to boot from any storage just stops with POST code 99 at the right bottom corner of the screen.

Another observation which could be useful.
My USB stick has activity LED. After the power is switched on, the LED blinks, then I can press DEL and enter to BIOS, but after I select in the BIOS this device and press Enter to start booting, the LED stops to blink.
When I use HDD as booting device, it behaves similarly. It starts spinning after power on, but after I select this device to boot from, it stops spinning.

I'd appreciate very much if you give me some efficient suggestions.
I wouldn't start RMA procedure and still hope the issue could be resolved with your help somehow...
Last edited by sshd on Wed Feb 17, 2021 10:41 pm, edited 1 time in total.

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

BTW if the system can't load any efi program after I falshed v1.22, how we can flash NVRAM (i.e. downgrade the BIOS)?

I connected serial console to the MB and see exactly the same text information which BIOS outputs on the display.
There are no any logs with debug info, no any CLI mode :(
Does H2+ support some "secret" side way to flash NVRAM?
And what does code 99 mean?
On the image you can see an attempt to boot from the single connected USB device:
Image
This is a "final" state, after that I can perform only power cycle or reset.
MotherBoard stops to work with keyboard and even serial console gets "Offline" status as you can see on the image.
I also checked how MB behaves with a single SODIMM. Result is the same :(

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

So no more help or advices from the odroid team?
Should I give up and consider my new H2+ is a useless brick? :cry:

User avatar
odroid
Site Admin
Posts: 38159
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2045 times
Been thanked: 1221 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by odroid »

sshd wrote:
Fri Feb 19, 2021 3:14 am
So no more help or advices from the odroid team?
Should I give up and consider my new H2+ is a useless brick? :cry:
Probably yes. :(

We needed some time to learn what '99' meant.
https://forums.tomshardware.com/threads ... o.3020751/

If we disabled the Quiet boot option, we could see '99' on the right-bottom corner with a USB drive boot menu as this picture. It booted fine from USB storage.
IMG_1082.JPG
IMG_1082.JPG (165.92 KiB) Viewed 2588 times
BTW, have you tried all four USB 2.0 and 3.0 host ports?
If yes, please contact "odroid at hardkernel dot com" with a URL of this thread.
They will help your RMA process if you purchased the board from our web-store directly.
Otherwise, contact your local distributor/reseller. Really sorry for the inconvenience caused.

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

odroid wrote:
Fri Feb 19, 2021 10:57 am
We needed some time to learn what '99' meant.
https://forums.tomshardware.com/threads ... o.3020751/
If we disabled the Quiet boot option, we could see '99' on the right-bottom corner with a USB drive boot menu as this picture. It booted fine from USB storage.
You are lucky to have booting possibility :)
Unfortunately it's not my case :(
odroid wrote:
Fri Feb 19, 2021 10:57 am
BTW, have you tried all four USB 2.0 and 3.0 host ports?
Yes, I tried. I think I tried almost all reasonable variants.
I changed the ports, I tried USB stick 2.0 and 3.0, I tried to reset BIOS settings putting out battery and PSU, I waited then more than 11minutes looking on the black screen. I tried to boot from SATA: HDD and SSD. I tried only one SODIMM in the first and second sockets. I tried to see what I can get via console from com0 and com1 ports. I even changed the monitor :) No luck so far.
odroid wrote:
Fri Feb 19, 2021 10:57 am
If yes, please contact "odroid at hardkernel dot com" with a URL of this thread.
They will help your RMA process if you purchased the board from our web-store directly.
Otherwise, contact your local distributor/reseller. Really sorry for the inconvenience caused.
I bought directly on your web-store.
I will contact ASAP.
Thanks for giving a hope... :)

Shadow0
Posts: 4
Joined: Fri Feb 12, 2021 6:09 am
languages_spoken: english
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by Shadow0 »

I'm sorry I didn't answer for a long time. I restored the system boot: I booted from a bootable USB flash drive and installed grub again.
I tried again to update the BIOS to version 1.22. After the update, the BIOS stops seeing the bootable USB flash drive. Disconnected hdd and nvme from motherboard. I checked the RAM for compatibility using the method from the wiki. The RAM turned out to be incompatible. Installed two sticks of RAM AMD Radeon R7 Performance Series [R7416G2400S2S-U] from the list of wiki "Confirmed RAM Modules". In BIOS version 1.22, something related to RAM has been changed: compatible RAM has become incompatible.
Here is the RAM data from dmidecode:

Code: Select all

# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.1.1 present.

Handle 0x0025, DMI type 17, 40 bytes
Memory Device
        Array Handle: 0x0023
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 16 GB
        Form Factor: DIMM
        Set: None
        Locator: A1_DIMM0
        Bank Locator: A1_BANK0
        Type: DDR4
        Type Detail: Synchronous
        Speed: 2400 MT/s
        Manufacturer: ABCD
        Serial Number: 1234
        Asset Tag: 9876543210
        Part Number: 123456789012345678
        Rank: Unknown
        Configured Memory Speed: 2400 MT/s
        Minimum Voltage: 1.1 V
        Maximum Voltage: 1.5 V
        Configured Voltage: 1.2 V

Handle 0x0027, DMI type 17, 40 bytes
Memory Device
        Array Handle: 0x0023
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 16 GB
        Form Factor: DIMM
        Set: None
        Locator: A1_DIMM1
        Bank Locator: A1_BANK1
        Type: DDR4
        Type Detail: Synchronous
        Speed: 2400 MT/s
        Manufacturer: ABCD
        Serial Number: 1234
        Asset Tag: 9876543210
        Part Number: 123456789012345678
        Rank: Unknown
        Configured Memory Speed: 2400 MT/s
        Minimum Voltage: 1.1 V
        Maximum Voltage: 1.5 V
        Configured Voltage: 1.2 V
To flash BIOS for version 1.12, I had to get the RAM from the laptop.
These users thanked the author Shadow0 for the post:
sshd (Mon Mar 01, 2021 9:58 pm)

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

Shadow0 wrote:
Sun Feb 28, 2021 11:46 pm
AMD Radeon R7 Performance Series [R7416G2400S2S-U] from the list of wiki "Confirmed RAM Modules". In BIOS version 1.22, something related to RAM has been changed: compatible RAM has become incompatible.
It's exactly my case, except I used 8GiB modules. Thank you for double-confirmation :)
Shadow0 wrote:
Sun Feb 28, 2021 11:46 pm
To flash BIOS for version 1.12, I had to get the RAM from the laptop.
Unfortunately I had no any compatible modules for downgrade.
I sent my MB back to Hardkernel and I do hope they would flash BIOS v1.12 or fix the issue in the latest version.
I wish they have a more precise QVL and testing of new BIOS releases.
Last edited by sshd on Fri Mar 05, 2021 11:02 pm, edited 1 time in total.

joshua.yang
Posts: 526
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 37 times
Been thanked: 162 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by joshua.yang »

Hi, @sshd. Sorry for the inconvenience. We just have received your H2 board.

In the test, I installed two Samsung 16GB RAM modules to boot. (https://www.hardkernel.com/shop/samsung ... 0-so-dimm/)
Then I entered BIOS for the first time but I saw that the paging performance (switching between the menus by the arrow keys) is quite slower than the other H2s I've ever seen on my test-use monitor.
So I thought that its BIOS seems partially corrupted so I flashed our v1.22 BIOS again.

Then I installed a NVMe (Windows installed), an eMMC (Ubuntu installed), and a SSD (Ubuntu installed) to the board.
I can boot from all the OS installed boot media and adjusting the boot sequence looks working well too.

I think I should downgrade its BIOS version to the v1.12 that is the version that you were able to boot from your environment before sending this back. How do you think about this?
While waiting for your answer, I will do a few further tests with this board.
These users thanked the author joshua.yang for the post (total 2):
sshd (Fri Mar 05, 2021 9:26 pm) • TurdFurguson (Sat Mar 06, 2021 1:12 am)

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

joshua.yang wrote:
Fri Mar 05, 2021 10:45 am
I saw that the paging performance (switching between the menus by the arrow keys) is quite slower than the other H2s I've ever seen on my test-use monitor.
So I thought that its BIOS seems partially corrupted so I flashed our v1.22 BIOS again.
Could it be that SPI flash chip used for BIOS has some defect or some problem with power supply?

After I upgraded BIOS I also sporadically saw that "paging performance". But I didn't found some pattern when it happens.
In a rare cases the picture was shown in lower resolution than usually. Usually BIOS displays a full screen resolution.
joshua.yang wrote:
Fri Mar 05, 2021 10:45 am
Then I installed a NVMe (Windows installed), an eMMC (Ubuntu installed), and a SSD (Ubuntu installed) to the board.
I can boot from all the OS installed boot media and adjusting the boot sequence looks working well too.
Great! Did you test the booting from USB as well?
joshua.yang wrote:
Fri Mar 05, 2021 10:45 am
I think I should downgrade its BIOS version to the v1.12 that is the version that you were able to boot from your environment before sending this back. How do you think about this?
I consider it as a forced temporary workaround.
I bought the RAM after a careful study of your RAM compatibility list.
And now I would have to stick to the old BIOS version.
It blocks me from buying your great 4 Ethernet port M.2 card, for instance.

Do you plan to fix your further BIOS versions and restore compatibility with AMD RADEON R7 RAM?
Or could you add the possibility into BIOS UI to tune RAM timings like in conventional motherboards?
joshua.yang wrote:
Fri Mar 05, 2021 10:45 am
While waiting for your answer, I will do a few further tests with this board.
More testing will be all for the better :)

Frankly speaking I like H2+ design and concept very much, but after using it a bit I have controversial impression regarding stability.
Even with BIOS v1.12 I had a couple of oddities:
1. I have one SanDisk USB 3.0 32GiB flash. Any other computers boot from it stably, but H2+ can't boot from it in ~50% cases.
I tried to install from this flash drive CentOS 8 and it seems some garbage was read, cause installed OS hung at some point.
But I could install the same CentOS 8 from 2 other USB drives: USB adapter with HDD and from very old Card Reader with miniSD card.
Note, the SanDisk USB drive in a perfect state, I checked it with `badblock` extensively w/o any issue on other PC.

2. After I installed CentOS 8 or other Linux (i.e. Manjaro) in rare cases during reboot I observed a couple of error messages printed on the screen with something regarding SATA. Unfortunately I didn't make a shot:(

Could I be so "lucky" that just got a bad H2+ sample?

Also it would be interesting to know in advance. What if the BIOS could be corrupted later again?
How can I re-flash that SPI-chip myself without sending MB again to Korea?
Unfortunately, the chip is soldered on the MB, but is it real to use SOIC8 adapter for reprogramming just on board?

I am sorry for so many questions :)
And thank you for the help :)
Last edited by sshd on Thu Mar 11, 2021 12:32 am, edited 1 time in total.
These users thanked the author sshd for the post:
TurdFurguson (Sat Mar 06, 2021 1:12 am)

Asterisk42
Posts: 1
Joined: Sun Nov 08, 2020 7:27 pm
languages_spoken: english
ODROIDs: Odroid H2+
Odroid N2
Has thanked: 0
Been thanked: 0
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by Asterisk42 »

Hi,

I have three Odroid h2+

I was able to update one to V1.22 and it works as expected.


I still have two from August 2020:
After a BIOS update from V1.10 to V1.22 every Linux I tried to boot from USB3 stick crashed with a kernel panic.
I was able to downgrade from BIOS V1.22 to V1.12, now everything works as before.
The third I have not yet updated.

I am now waiting for a new update.
Best regards,
photo_2021-03-06_08-32-44.jpg
photo_2021-03-06_08-32-44.jpg (209.11 KiB) Viewed 2330 times

joshua.yang
Posts: 526
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 37 times
Been thanked: 162 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by joshua.yang »

sshd wrote:
Fri Mar 05, 2021 10:52 pm
Could it be that SPI flash chip used for BIOS has some defect or some problem with power supply?

After I upgraded BIOS I also sporadically saw that "paging performance". But I didn't found some pattern when it happens.
In a rare cases the picture was shown in lower resolution than usually. Usually BIOS displays a full screen resolution.
In fact, I have not seen this symptom on the other board so far but as a typical electric board goes I think it can happen. :?:
I believe it is a BIOS problem since the H2 boards can operate even with the other power supply having slightly low voltage than the recommended one without any accessories like SATA drives. This is very dangerous, do not attempt to do this. ;)
sshd wrote:
Fri Mar 05, 2021 10:52 pm
Great! Did you test the booting from USB as well?
Sure. I can install several OSs through the USB 3.0 port.
sshd wrote:
Fri Mar 05, 2021 10:52 pm
I consider it as a forced temporary workaround.
I bought the RAM after a careful study of your RAM compatibility list.
And now I would have to stick to the old BIOS version.
It blocks me from buying your great 4 Ethernet port M.2 card, for instance.
Once again, we are sorry for the inconvenience.
I will send you back with v1.12 BIOS installed for now.
sshd wrote:
Fri Mar 05, 2021 10:52 pm
Do you plan to fix your further BIOS versions and restore compatibility with AMD RADEON R7 RAM?
Or could you add the possibility into BIOS UI to tune RAM timings like in conventional motherboards?
We'd like to, but before that, we should have an AMD Radeon R7 RAM on our hands first. If we buy one, would test with this in the future.
But I cannot make sure it will happen. :(
sshd wrote:
Fri Mar 05, 2021 10:52 pm
More testing will be all for the better :)

Frankly speaking I like H2+ design and concept very much, but after using it a bit I have controversial impression regarding stability.
Even with BIOS v1.12 I had a couple of oddities:
1. I have one SanDisk USB 3.0 32GiB flash. Any other computers boot from it stably, but H2+ can't boot from it in ~50% cases.
I tried to install from this flash drive CentOS 8 and it seems some garbage was read, cause installed OS hung at some point.
But I could install the same CentOS 8 from 2 other USB drives: USB adapter with HDD and from very old Card Reader with miniSD card.
Note, the SanDisk USB drive in a perfect state, I checked it with `badblock` extensively w/o any issue on other PC.

2. After I installed CentOS 8 or other Linux (i.e. Manjaro) in rare cases during reboot I observed a couple of error messages printed on the screen with something regarding SATA. Unfortunately I didn't make a shot:(

Could I be so "lucky" that just got a bad H2+ sample?
Thank you for the positive opinion of our board.

I will test with CentOS as well. I'm planning to test installing several major OS like Manjaro and Fedora and running Ubuntu live USB.
If any defects found, I will tell our team about this and the appropriate treats will be taken.
sshd wrote:
Fri Mar 05, 2021 10:52 pm
Also it would be interesting to know in advance. What if the BIOS could be corrupted later again?
How can I re-flash that SPI-chip myself without sending MB again to Korea?
Unfortunately, the chip is wired on the MB, but is it real to use SOIC8 adapter for reprogramming just on board?

I am sorry for so many questions :)
And thank you for the help :)
As far as I know, there's no way to re-flash BIOS on the home. I heard that there's special hardware to flash this.
I'll find out and let you know that. By the way, when I downgrade your H2 BIOS I used Samsung RAM modules. I didn't use the special hardware.
I believe that the Samsung RAM is enough to repair BIOS in this case unless BIOS is totally corrupted.

Please don't hesitate to ask. I hope that these answers will help you. :)
Last edited by joshua.yang on Mon Mar 08, 2021 11:29 am, edited 1 time in total.

joshua.yang
Posts: 526
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 37 times
Been thanked: 162 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by joshua.yang »

Asterisk42 wrote:
Sat Mar 06, 2021 4:36 pm
Hi,

I have three Odroid h2+

I was able to update one to V1.22 and it works as expected.


I still have two from August 2020:
After a BIOS update from V1.10 to V1.22 every Linux I tried to boot from USB3 stick crashed with a kernel panic.
I was able to downgrade from BIOS V1.22 to V1.12, now everything works as before.
The third I have not yet updated.

I am now waiting for a new update.
Best regards,

photo_2021-03-06_08-32-44.jpg
Thanks for the report, and sorry for the inconvenience. If you have trouble with v1.22 BIOS, please keep using v1.12 instead for now.

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

joshua.yang wrote:
Mon Mar 08, 2021 10:47 am
In fact, I have not seen this symptom on the other board so far but as a typical electric board goes I think it can happen. :?:
I believe it is a BIOS problem since the H2 boards can operate even with the other power supply having slightly low voltage than the recommended one without any accessories like SATA drives. This is very dangerous, do not attempt to do this. ;)
I use PSU bought on Hardkerlen web-store, so 14V, 60W should be more than enough for all connected devices I guess.
Actually my question was rather a hint to replace my MB sample by new one if it has some defect :D
joshua.yang wrote:
Mon Mar 08, 2021 10:47 am
Sure. I can install several OSs through the USB 3.0 port.
Great. But I will be positively surprised if my problematic with H2+ SanDisk USB3 works properly after I get back the MB.
joshua.yang wrote:
Mon Mar 08, 2021 10:47 am
Once again, we are sorry for the inconvenience.
I will send you back with v1.12 BIOS installed for now.
I believe vast majority of Harkernel users are so called "enthusiasts" which are ready for some "surprises", so NP :)
When do you plan to send?
And could I "merge" the parcel with MB and with buying 32GiB eMMC just to save money for posting?
You can just insert eMMC into MB...
joshua.yang wrote:
Mon Mar 08, 2021 10:47 am
...we should have an AMD Radeon R7 RAM on our hands first. If we buy one, would test with this in the future.
But I cannot make sure it will happen. :(
I do hope you have that model on local market, if not we could help each other...
joshua.yang wrote:
Mon Mar 08, 2021 10:47 am
By the way, when I downgrade your H2 BIOS I used Samsung RAM modules. I didn't use the special hardware.
I believe that the Samsung RAM is enough to repair BIOS in this case unless BIOS is totally corrupted.
We know this now, but when I got a trouble I was not completely sure that Samsung RAM could be remedy.
And buying the new RAM just to downgrade BIOS looks quite expensive especially if I have no other hardware where I can utilize AMD R7 SODIMMs ;)
That SOIC8 tool is much more cheaper.
So just consider a wish to have more easy possibility to reflash BIOS NVRAM as suggestion for possible further H/W updates.
If the chip is not soldered, but placed in the socket it could be ideal variant.
Last edited by sshd on Thu Mar 11, 2021 12:34 am, edited 1 time in total.

User avatar
odroid
Site Admin
Posts: 38159
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2045 times
Been thanked: 1221 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by odroid »

Our web-store system has no option to remove the shipping cost.
But try contacting our sales team via "odroid at hardkernel dot com" to ask a workaround.

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

odroid wrote:
Wed Mar 10, 2021 11:55 am
...try contacting our sales team...
Thanks, they were contacted me and I confirmed that I'd like to order eMMC 32GB for H2+.
If you have a possibility, could you please check that my MB with restored BIOS v1.12 can boot from the eMMC?
Then you could leave eMMC installed on the MB.
Thank you in advance:)

joshua.yang
Posts: 526
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 37 times
Been thanked: 162 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by joshua.yang »

sshd wrote:
Thu Mar 11, 2021 9:37 am
Thanks, they were contacted me and I confirmed that I'd like to order eMMC 32GB for H2+.
If you have a possibility, could you please check that my MB with restored BIOS v1.12 can boot from the eMMC?
Then you could leave eMMC installed on the MB.
Thank you in advance:)
Hi.

I have tested that your new 32GB eMMC works with your H2 board that is v1.12 BIOS installed.
I installed Ubuntu into the eMMC using an USB installer drive and could boot from the eMMC. So, at least two ways for booting are verified one more time. :)
I didn't erase the eMMC so you can boot into the Ubuntu in the eMMC right after turning your H2 on.

We're preparing your parcel, you will receive that soon. Thanks.
These users thanked the author joshua.yang for the post:
sshd (Thu Mar 11, 2021 8:26 pm)

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

joshua.yang wrote:
Thu Mar 11, 2021 4:37 pm
I installed Ubuntu into the eMMC using an USB installer drive and could boot from the eMMC. So, at least two ways for booting are verified one more time. :)
We're preparing your parcel, you will receive that soon. Thanks.
Thank you very much for the testing that and for the support.
I got the tracking number already. Crossing the fingers and looking forward to get back working MB:)

sshd
Posts: 13
Joined: Mon Feb 15, 2021 9:19 pm
languages_spoken: english
ODROIDs: H2+
Has thanked: 8 times
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by sshd »

Forgot to inform.
~a month ago I received MB. Thanks, works fine now. CentOS 8 works perfectly despite I had to use dkms for LAN driver.
The MB lives with old BIOS 1.12 still.
I saw that never than 1.22 version was released with other DRAM vendors support/fix.
Do you think the new BIOS should work with my AMD Radeon R748G2400S2S-U, 2x8=16GiB?
Just in case I bought and tested on other spare H/W the SPI programmer (like this https://wiki.odroid.com/odroid-h2/hardw ... mer#wiring) :)

User avatar
odroid
Site Admin
Posts: 38159
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2045 times
Been thanked: 1221 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by odroid »

The latest BIOS version 1.23 probably works with your Radeon DRAM. But, it is very hard to guarantee since we don't have the same DRAM module.

Anyway, if you have the SPI programmer and look into this thread, it is worth to try the latest BIOS safely.
viewtopic.php?f=173&t=41875

asch
Posts: 1
Joined: Thu Jul 08, 2021 5:22 am
languages_spoken: english, russian
ODROIDs: ODROID H2+
Has thanked: 0
Been thanked: 1 time
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by asch »

odroid wrote:
Thu May 20, 2021 10:36 am
The latest BIOS version 1.23 probably works with your Radeon DRAM. But, it is very hard to guarantee since we don't have the same DRAM module.

Anyway, if you have the SPI programmer and look into this thread, it is worth to try the latest BIOS safely.
viewtopic.php?f=173&t=41875
Hi!

Just a quick heads-up: 1.23 does not fix issues with AMD RAM.
My story: I decided to update my H2+ to 1.23 from 1.12. It has 8 GB RAM (one AMD Radeon R748G2400S2S-UO module, 1.2v 16-16-16-36 timings). The PC was working perfectly fine before the update. As a result, I cannot boot (stuck at Hardkernel logo, bios code 99). I can enter BIOS by mashing Esc key, however it won't boot any media. I tried clearing CMOS, "Save and exit" and all other options, but it still hangs after selecting my USB thumb drive.
As a result I had to buy a used Samsung M471A5644EB0-CRC 2 GB module, which allowed me to boot successfully and downgrade to 1.12. After this downgrade, it boots fine with the AMD memory module.

I'd like to ask you to put a warning on wiki, so that people would think twice before upgrading the BIOS to 1.23.

P.S. Great SBC otherwise, really enjoy it. In fact, it became my main PC at the moment.
These users thanked the author asch for the post:
sshd (Sat Jul 24, 2021 4:12 am)

User avatar
odroid
Site Admin
Posts: 38159
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2045 times
Been thanked: 1221 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by odroid »

@asch,

Thank you for sharing your experiences and suggestion.
I've added a red colored warning message to the WiKi page.
https://wiki.odroid.com/odroid-h2/hardw ... lk-esf_123

human
Posts: 11
Joined: Sun May 02, 2021 3:52 am
languages_spoken: english
ODROIDs: C2, C4, HC1, H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by human »

Hello

I have the same issue, after upgrading to 1.23, with 1x 16GB Kingston KVR24S17D8/16 RAM, it doesn't boot, two blue and one red led are constantly on, no amber or any other signals. Trying cold boot all day no results.

So I'm facing to options: manually program the BIOS chip or find compatible RAM?

Do we know of a RAM stick that boots in this state?

User avatar
odroid
Site Admin
Posts: 38159
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2045 times
Been thanked: 1221 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by odroid »

Try sourcing/borrowing a Samsung or Hynix RAM.

BTW, have you removed the backup battery and waited around 10 minutes when you did a cold boot?

human
Posts: 11
Joined: Sun May 02, 2021 3:52 am
languages_spoken: english
ODROIDs: C2, C4, HC1, H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by human »

Yes, I unplugged everything (battery, emmc, USB, m.2...), left it overnight, then just plugged in the power and HDMI. Nothing. I wait for more that 10 min at boot for the RAM timings to settle, but still no video output, not even USB power.
I can't actually turn it off, if I hold the power button the lights go off after a couple of seconds, but as soon as I let the button go they turn back on.

I just wanted to say that I really like your products, they are purposefull, well made and maintained, and I use them daily, they form the backbone of work and fun as servers and media players. Great work and thank you for all the support!

That being said... 2 of 4 (H2+, C4 / HC1, C2) now have had critical issues and supply chains being what they are atm I can't even replace them.
viewtopic.php?f=207&t=42475

Buy Hardkernel products in bulk people! ;)

I'll report my RAM findings and if you need any more info for troubleshooting let me know, thank you.
These users thanked the author human for the post:
odroid (Tue Oct 05, 2021 11:17 am)

human
Posts: 11
Joined: Sun May 02, 2021 3:52 am
languages_spoken: english
ODROIDs: C2, C4, HC1, H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: Can't boot anymore after upgrading bios to 1.22

Post by human »

It lives!

Samsung M471A1K43CB1-CTD works, with BIOS 1.23.
Downgraded to 1.12, both sticks (+1x 16GB Kingston KVR24S17D8/16) work together now.

Thank you again and sad to hear...
https://www.hardkernel.com/shop/odroid-h2plus/
Hopefully you're working on a replacement :D :roll:
These users thanked the author human for the post:
odroid (Tue Oct 12, 2021 11:09 am)

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 1 guest