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

T430 Memory Frequency Bricks Board #24

Closed
WillAndersonWA opened this issue Feb 4, 2020 · 8 comments
Closed

T430 Memory Frequency Bricks Board #24

WillAndersonWA opened this issue Feb 4, 2020 · 8 comments

Comments

@WillAndersonWA
Copy link

WillAndersonWA commented Feb 4, 2020

After changing the memory frequency on my test T430 to 1066MHz I found that the board would refuse to boot ever again, removing the CMOS battery and main battery, power cycling it, absolutely nothing would work, I'm trying to see if I can flash coreboot via hardware to recover this board.

Note, had 8GB + 4GB of Samsung 1866MHz CL10 RAM Installed at the time, will not boot regardless of the RAM installed in any config.

@an94baller
Copy link

I can confirm that the issue is valid, the only solution is to not use 1066 memory strap, this cannot be fixed by any soft resets as you mentioned.

Maybe as part of the bios modification we can hide 1066 strap or delete the ability for users to select it?

Source: had to borrow n4ru's RPI to unbrick mine (flashing stock bios backup)

@datNoko
Copy link

datNoko commented Feb 4, 2020

As stated in the Readme "Worst case scenario, you can flash a backup or fresh BIOS using a hardware programmer." so i guess flashing it with hardware will work. If the memory in the bios was changed to 1066Mhz for a single channel then you got 2132 on dual channel. Maybe the memory cant handle it.

@an94baller
Copy link

an94baller commented Feb 4, 2020

As stated in the Readme "Worst case scenario, you can flash a backup or fresh BIOS using a hardware programmer." so i guess flashing it with hardware will work. If the memory in the bios was changed to 1066Mhz for a single channel then you got 2132 on dual channel. Maybe the memory cant handle it.

I don't think that's how it works

@n4ru
Copy link
Owner

n4ru commented Feb 4, 2020

This is not an 1vyrain issue, but this is indeed now confirmed to brick. I have personally fixed another user's T430 by hardware flashing a BIOS backup (though you can also flash any patched 4MB BIOS, don't even need a backup).

I'll add a giant warning and add this to the list of things to add to the FAQ. Please be cautious with the advanced menu, but in my years of use I have not encountered any other brick like this.

@digmorepaka
Copy link
Collaborator

Just for future reference, this is not an issue of the frequency limiter, but issue of the actual ram initialization. A user reported their machine not booting with 1066 dimms installed, and as expected with a 1333 dimm it did work correctly.

@an94baller
Copy link

Just for future reference, this is not an issue of the frequency limiter, but issue of the actual ram initialization. A user reported their machine not booting with 1066 dimms installed, and as expected with a 1333 dimm it did work correctly.

I put 2133 ram which works on my T430, setting to 1066 in memory limiter does brick the machine

I'm not sure why/how/what's wrong with 1066 strap being broken on these machines

@adrianparvino
Copy link

I'm the user, just for reference.

@n4ru
Copy link
Owner

n4ru commented Feb 21, 2020

Closing this now, the Long Form FAQ contains a warning to avoid this memory timing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants