#527 Issue booting T400

Closed
opened 5 months ago by mushi · 5 comments
mushi commented 5 months ago

I recently liberated my T400 but after turning it on I noticed it would not boot.It has been flashed with a BBB using txt and vesafb both do not work for me at the moment.When flashed, flashrom gave me 'Verifying flash... VERIFIED.' I have tried removing all power sources, trying two different sizes of ram (not together), and using only one slot of ram.Additionally the screen blinks/flickers the color black and the fan comes on shortly before turning off.I'm eager to fix this issue and provide more information if necessary.

PS:One possibly important detail is that I was unsure whether or not to use ich9fdgbe_8m.bin or ich9fdnogbe_8m.bin so I went with fdgbe.

I recently liberated my T400 but after turning it on I noticed it would not boot.It has been flashed with a BBB using txt and vesafb both do not work for me at the moment.When flashed, flashrom gave me 'Verifying flash... VERIFIED.' I have tried removing all power sources, trying two different sizes of ram (not together), and using only one slot of ram.Additionally the screen blinks/flickers the color black and the fan comes on shortly before turning off.I'm eager to fix this issue and provide more information if necessary. PS:One possibly important detail is that I was unsure whether or not to use ich9fdgbe_8m.bin or ich9fdnogbe_8m.bin so I went with fdgbe.
Andrew Robbins commented 5 months ago
Collaborator

Try flashing with the ROM we distribute before attempting to modify it to use your board's real MAC address, then get back to us on how that went. Make sure you're using the correct ROM for your flash chip size. You can look for the flash chip size in the output of flashrom when you have your BBB connected to the board:

# ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512

Also, the difference between 'fdgbe' (Firmware Discriptor Gigabit Ethernet) and 'fdnogbe' is that the 'nogbe' version does not contain the firmware for the ethernet NIC on the board, meaning that ethernet will NOT work if you use it.

These sorts of issues are best handled in Libreboot's IRC channel #libreboot on Freenode, if you would prefer to join us there. Otherwise, I can assist here but there will be longer delays.

Try flashing with the ROM we distribute before attempting to modify it to use your board's real MAC address, then get back to us on how that went. Make sure you're using the correct ROM for your flash chip size. You can look for the flash chip size in the output of flashrom when you have your BBB connected to the board: # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 Also, the difference between 'fdgbe' (**F**irmware **D**iscriptor **G**iga**b**it **E**thernet) and 'fdnogbe' is that the 'nogbe' version does not contain the firmware for the ethernet NIC on the board, meaning that ethernet will NOT work if you use it. These sorts of issues are best handled in Libreboot's IRC channel `#libreboot` on Freenode, if you would prefer to join us there. Otherwise, I can assist here but there will be longer delays.
mushi commented 5 months ago
Poster

I tried the distributed rom without any modifications and once again I had the same result or similar.There would be power and then the CapsLk+NmLk light would turn on briefly before turning off and repeating this pattern.I tried this motherboard out with the original bios(which I've backed up) first and it worked as expected so it can't be the board unless I've damaged it since then, which I doubt.I can share the output of flashrom if I must but this is my first time using notabug and I'm not sure how to separate it from the rest of my text.Another note I did not compile flashrom from source.Also thanks for the recommendation but I'm not a fan of Freenode.

I tried the distributed rom without any modifications and once again I had the same result or similar.There would be power and then the CapsLk+NmLk light would turn on briefly before turning off and repeating this pattern.I tried this motherboard out with the original bios(which I've backed up) first and it worked as expected so it can't be the board unless I've damaged it since then, which I doubt.I can share the output of flashrom if I must but this is my first time using notabug and I'm not sure how to separate it from the rest of my text.Another note I did not compile flashrom from source.Also thanks for the recommendation but I'm not a fan of Freenode.
Tonux commented 5 months ago

I recently flashed my T400 as well and had a very similar problem to this. I fixed this by re-seating the RAM, as coreboot is more suspicious to this than vendor BIOS, I would assume this is true in Libreboot.

I recently flashed my T400 as well and had a very similar problem to this. I fixed this by re-seating the RAM, as coreboot is more suspicious to this than vendor BIOS, I would assume this is true in Libreboot.
mushi commented 4 months ago
Poster

I've tried re seating the RAM to no avail.All sizes 1,2, and 4 GB are all SAMSUNG.Could this be the issue?

I've tried re seating the RAM to no avail.All sizes 1,2, and 4 GB are all SAMSUNG.Could this be the issue?
mushi commented 3 months ago
Poster

I've solved the issues since purchasing a new laptop(LOL).Turns out it was a problem with the RAM.Between all 8 of them only two work(both are 2GB) so I'll have 4GB instead of the expected 8, but at least it works now.

I've solved the issues since purchasing a new laptop(LOL).Turns out it was a problem with the RAM.Between all 8 of them only two work(both are 2GB) so I'll have 4GB instead of the expected 8, but at least it works now.
Sign in to join this conversation.
Loading...
Cancel
Save
There is no content yet.