Skip to content
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

Trouble booting some RAM configs on V560TU #925

Closed
filipleple opened this issue Jul 2, 2024 · 5 comments
Closed

Trouble booting some RAM configs on V560TU #925

filipleple opened this issue Jul 2, 2024 · 5 comments
Assignees
Labels
bug Something isn't working firmware novacustom_v56_mtl NovaCustom V56 Series

Comments

@filipleple
Copy link
Member

filipleple commented Jul 2, 2024

Component

Dasharo firmware

Device

NovaCustom V56 14th Gen

Dasharo version

v0.9.0-rc6

Dasharo Tools Suite version

No response

Brief summary

Certain RAM configs will refuse to boot on V560TU - Intel Core Ultra 7 155H, or will boot only following a CMOS reset

How reproducible

70%

How to reproduce

Try to boot

  • 2x16GB
  • 32GB & 16GB
  • 48GB & 32GB

Expected behavior

They should boot

Actual behavior

Most of the time, 2x16GB boots only after a CMOS reset, 32GB & 16GB won't boot no matter what and cause the power LED and keyboard backlight to flash. However, it's not 100% reproducible.

Screenshots

No response

Additional context

No response

Solutions you've tried

No response

@filipleple filipleple added bug Something isn't working firmware needs review novacustom_v56_mtl NovaCustom V56 Series labels Jul 2, 2024
@mkopec
Copy link
Member

mkopec commented Jul 2, 2024

@filipleple Do you recall the CPU model of the affected laptop? Both combinations seem to work fine on V540TU w/ 155H on my end

@filipleple
Copy link
Member Author

updated the issue to include the cpu model

@mkopec
Copy link
Member

mkopec commented Jul 3, 2024

I believe there is an issue with MRC cache invalidation. On some RAM swaps, instead of invalidating cached MRC settings and re-training, FSP attempts to restore FSP settings which and fails. As a workaround, one can remove one memory module and boot with just the other one installed.

@mkopec
Copy link
Member

mkopec commented Jul 4, 2024

soo, apparently the 16GB and 32GB modules produce the exact same SPD CRC, so FSP considers them the same and doesn't invalidate MRC cache. It seems like the RAM manufacturer is at fault here for not assigning an unique serial number to each module

@mkopec
Copy link
Member

mkopec commented Jul 5, 2024

Workaround: Dasharo/coreboot@d7eb079

Confirmed to resolve the retraining issue. Users are expected to clear the CMOS when swapping memory modules

@mkopec mkopec closed this as completed Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working firmware novacustom_v56_mtl NovaCustom V56 Series
Projects
None yet
Development

No branches or pull requests

3 participants