-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
T430s port #723
T430s port #723
Conversation
Guess you are right. Though I won't drop it yet, but will look for a way in which the patch can be applied in the board config. |
@Siproqu the same debate happened for x230 and nvram. The decision that happened there was that if a user wants to change NVRAM values, he could build nvram payload and change at runtime. The new commited board changes for x230 reflects the required changes. Those values should be changeable from the nvram payload. (See #670) I would advise creating the t430s and t430s-nvramtool boards if you want, and document in the board configuration file that the linked coreboot config for t430s-nvramtool includes the nvramtool tool to permit the XYZ changes you intended to apply to the board following your use case. Those boards, for example, require the nvramtol to deactivate second GPU and keep the integrated GPU alive only. So there is examples and documentation in issues toward a similar implementation for a different use case. Hope that helps! |
6e19100
to
3deac32
Compare
Half successfully tested. Coreboot and Heads work as fine (no serious problems). First problem: The gpg-card couldn't be reset (I use a Nitrokey start). Though this is probably a problem with the Nitrokey. I had to generate new keys on it and export the key manually to make the reset work again. Is there any way to read the logs/printed text of the commands before the GUI comes up again? |
The Nitrokey Start (and Gnuk devices) working a bit differently regarding key generation and PIN chaning etc. You may run into this problem (see here) If this is not the problem here, more information would be necessary to decide if it is more suitable on NK Start repo or here. |
Now requires this addition in board config: |
I mainly followed this page which has basic information about the flash layout and two pictures where the SOIC-8 chip is located. The pin layout for the chip I have on my board (MX25L12835F/MX25L12845E/MX25L12865E) can be found here or in the board view file (I will push it later this day). One can open the file with Open Board View. When it comes to the actual disassembling of the laptop, I mainly followed the official repair manual. It won't cover the removal of the main board though. Maybe I will add some pictures later where the screws are located. Back then I removed all screws on the main board which were marked with an little arrow/triangle. Now you can remove the main board and flip it around. The SOIC-8 chip is located under the black foil. Hope this helps. |
@Siproqu That would be awesome information for a PR to this page!
Most of it is already done per @Thrilleratplay work and merged under http://osresearch.net/Install-and-Configure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please review! :)
|
||
If you do not want to use the extract.sh script for blob extraction, you can also extract the blobs with _dd_: | ||
``` | ||
$ dd if=eprom_read_1.bin of=gbe.bin skip=8 count=16 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is done per ifdtool, you can look at x220 and t420 extract scripts. To maximize space of BIOS region, you can look at #877
cd "$extractdir" | ||
$IFDTOOL -x $bioscopy | ||
cp "$extractdir/flashregion_3_gbe.bin" "$BLOBDIR/gbe.bin" | ||
$MECLEAN -O "$BLOBDIR/me.bin" -r -t "$extractdir/flashregion_2_intel_me.bin" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. Please look at #877
@@ -0,0 +1,15851 @@ | |||
dd:1.3?,r?-=bb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this binary redistributable?
@@ -0,0 +1,286 @@ | |||
# |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please generate this config with
cp config/coreboot-t430s.config build/coreboot-ver/.config
cd build/coreboot-ver/
make savedefconfig
cp defconfig ../../config/coreboot-t430s.config
git add ../../config/coreboot-t430s.config
So that it contains only deviations from std coreboot config
export CONFIG_BOOT_KERNEL_REMOVE="quiet" | ||
export CONFIG_BOOT_DEV="/dev/sda1" | ||
export CONFIG_BOOT_GUI_MENU_NAME="ThinkPad T430s Heads Boot Menu" | ||
export CONFIG_WARNING_BG_COLOR="--background-gradient 0 0 0 150 125 0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those are not necessary anymore
Also adding t430s #692 and adding your name as a tester/contributor unless you ask me to remove you there. |
I will review it during weekend.
No problem at all. I am happy to help where I can. |
Is replaced with coreboot 4.12 version. |
No description provided.