Skip to content

Adding entry for the X280 to heads-wiki - #227

Merged
tlaurion merged 1 commit into
linuxboot:masterfrom
NobodyNo0ne:master
Sep 1, 2026
Merged

Adding entry for the X280 to heads-wiki#227
tlaurion merged 1 commit into
linuxboot:masterfrom
NobodyNo0ne:master

Conversation

@NobodyNo0ne

Copy link
Copy Markdown
Contributor

This is just a preliminary guide for X280 flashing. I took the layout from the T480s guidance.
Images added.

@tlaurion

Copy link
Copy Markdown
Collaborator

@NobodyNo0ne please follow https://osresearch.net/Contributing-to-Heads-wiki/#testing-changes-on-github

This requires to configure github to render pages as defined there and hten push back changes to trigger github rebuild and rendering of this pr against your github page.

Then update OP with links to rendered page with changes upon merged. Thanks!

@NobodyNo0ne

NobodyNo0ne commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

@NobodyNo0ne please follow https://osresearch.net/Contributing-to-Heads-wiki/#testing-changes-on-github

This requires to configure github to render pages as defined there and hten push back changes to trigger github rebuild and rendering of this pr against your github page.

Then update OP with links to rendered page with changes upon merged. Thanks!

https://osresearch.net/Contributing-to-Heads-wiki/#testing-changes-on-github points to https://pmarsceill.github.io/just-the-docs/ which seems like a broken link to me (404).
https://github.com/just-the-docs/just-the-docs might be a better link?
the command gem install just-the-docs seems to work <- I have it setup in my browser now, so its just that link.

I should add

Verifying broken links

Please verify https://YOUR_USERNAME_HERE.github.io/heads-wiki/ with https://validator.w3.org/checklink prior of pushing your changes.

I actually DO see this, just trying to fix CircleCI on the actual port PR

@tlaurion

Copy link
Copy Markdown
Collaborator

@NobodyNo0ne

Copy link
Copy Markdown
Contributor Author

https://pmarsceill.github.io/

https://pmarsceill.github.io/ i don't see this @NobodyNo0ne

In the wiki:

Prerequisites

For larger changes, multiple changes and that may require adding new pages, it is strongly suggested to set up a local Jekyll instance. Please refer to Jekyll’s installation documentation to setup it up on your system. You will need to install ruby and gems.

Additionally, the theme will also need to be installed as the remote theme does not seem to work with locally severed Jekyll instances. Instructions for installing the Just the Docs theme can be found here.

So there is no direct link to docs for the theme.

@NobodyNo0ne

Copy link
Copy Markdown
Contributor Author

I have no idea how I got the domain working but it wasn't through pages as the Wiki said I should. I still need to fix CircleCI as well

@NobodyNo0ne
NobodyNo0ne force-pushed the master branch 2 times, most recently from 42c4117 to a9ea3e1 Compare August 27, 2026 16:53
@tlaurion

tlaurion commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

I see the page rendered at https://nobodyno0ne.github.io/heads-wiki-x280/X280s-maximized-flashing/

I guess the docs should say "heads-wiki-repo-name" sicne you created a different project name, heads-wiki is not good anymore per docs. Or you had different issue? not sure I follow.

Please clean up commits :)

@NobodyNo0ne

NobodyNo0ne commented Aug 27, 2026

Copy link
Copy Markdown
Contributor Author

I see the page rendered at https://nobodyno0ne.github.io/heads-wiki-x280/X280s-maximized-flashing/

I guess the docs should say "heads-wiki-repo-name" sicne you created a different project name, heads-wiki is not good anymore per docs. Or you had different issue? not sure I follow.

Please clean up commits :)

How did I manage to put 'X280s'?
I think the issue was that I named my fork 'heads-wiki-x280' so GitHub took that and went along with it. Not sure if I should rename the repo, am sure that 'X280s' is very wrong.

Did a rebase/soft reset to squash commits. Fixed URL typo. I think it just uses the repo name by default, not used GitHub pages before.

@NobodyNo0ne

NobodyNo0ne commented Aug 27, 2026

Copy link
Copy Markdown
Contributor Author

I think I do actually need to remove the CNAME for Pages to work as described in docs <- I do

@tlaurion

Copy link
Copy Markdown
Collaborator

I see the page rendered at https://nobodyno0ne.github.io/heads-wiki-x280/X280s-maximized-flashing/

I guess the docs should say "heads-wiki-repo-name" sicne you created a different project name, heads-wiki is not good anymore per docs. Or you had different issue? not sure I follow.

Please clean up commits :)

How did I manage to put 'X280s'?
I think the issue was that I named my fork 'heads-wiki-x280' so GitHub took that and went along with it. Not sure if I should rename the repo, am sure that 'X280s' is very wrong.

Did a rebase/soft reset to squash commits. Fixed URL typo. I think it just uses the repo name by default, not used GitHub pages before.

Can't see rendered page since CNAME removed and definitely should not be removed.

Where do you see your page rendered?

@NobodyNo0ne

Copy link
Copy Markdown
Contributor Author

I see the page rendered at https://nobodyno0ne.github.io/heads-wiki-x280/X280s-maximized-flashing/
I guess the docs should say "heads-wiki-repo-name" sicne you created a different project name, heads-wiki is not good anymore per docs. Or you had different issue? not sure I follow.
Please clean up commits :)

How did I manage to put 'X280s'?
I think the issue was that I named my fork 'heads-wiki-x280' so GitHub took that and went along with it. Not sure if I should rename the repo, am sure that 'X280s' is very wrong.
Did a rebase/soft reset to squash commits. Fixed URL typo. I think it just uses the repo name by default, not used GitHub pages before.

Can't see rendered page since CNAME removed and definitely should not be removed.

Where do you see your page rendered?

For some reason, for me https://nobodyno0ne.github.io/heads-wiki-x280/ is only visible if I remove/rename CNAME?

@tlaurion

Copy link
Copy Markdown
Collaborator

I see the page rendered at https://nobodyno0ne.github.io/heads-wiki-x280/X280s-maximized-flashing/
I guess the docs should say "heads-wiki-repo-name" sicne you created a different project name, heads-wiki is not good anymore per docs. Or you had different issue? not sure I follow.
Please clean up commits :)

How did I manage to put 'X280s'?
I think the issue was that I named my fork 'heads-wiki-x280' so GitHub took that and went along with it. Not sure if I should rename the repo, am sure that 'X280s' is very wrong.
Did a rebase/soft reset to squash commits. Fixed URL typo. I think it just uses the repo name by default, not used GitHub pages before.

Can't see rendered page since CNAME removed and definitely should not be removed.

Where do you see your page rendered?

For some reason, for me https://nobodyno0ne.github.io/heads-wiki-x280/ is only visible if I remove/rename CNAME?

It's visible now without the s

https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/

@NobodyNo0ne

NobodyNo0ne commented Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

I see the page rendered at https://nobodyno0ne.github.io/heads-wiki-x280/X280s-maximized-flashing/
I guess the docs should say "heads-wiki-repo-name" sicne you created a different project name, heads-wiki is not good anymore per docs. Or you had different issue? not sure I follow.
Please clean up commits :)

How did I manage to put 'X280s'?
I think the issue was that I named my fork 'heads-wiki-x280' so GitHub took that and went along with it. Not sure if I should rename the repo, am sure that 'X280s' is very wrong.
Did a rebase/soft reset to squash commits. Fixed URL typo. I think it just uses the repo name by default, not used GitHub pages before.

Can't see rendered page since CNAME removed and definitely should not be removed.
Where do you see your page rendered?

For some reason, for me https://nobodyno0ne.github.io/heads-wiki-x280/ is only visible if I remove/rename CNAME?

It's visible now without the s

https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/

Oh right, yeah the s wasn't meant to be there. I must have done that late in the night. I will undo the CNAME change for final PR. If renaming it lets you see it, then that's probably better?

Should I open a new issue for some of this? The broken links and such.

@NobodyNo0ne

NobodyNo0ne commented Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

Also, in the docs I have (still preliminary), I know flashprog is the better choice (at least I prefer it), but most distros package flashrom instead. I think Arch has flashprog?
Debian seems to have flashrom, Fedora seems to have flashrom, I have not checked other notable distros (like OpenSUSE package repos) yet. So its probably safer to assume a user reading the guide is using flashrom

also realised that heads won't default to 25.09 after this so I need to remove that note.

I'm not the best at writing, but everything that needs to be there, is there. I don't want to sit on this making small changes to how I have sentences written one by one.

@NobodyNo0ne
NobodyNo0ne marked this pull request as ready for review August 29, 2026 00:26
@NobodyNo0ne NobodyNo0ne changed the title Preliminary guide based off of T480s Adding entry for the X280 to heads-wiki Aug 29, 2026
@tlaurion

Copy link
Copy Markdown
Collaborator

https://pmarsceill.github.io/

https://pmarsceill.github.io/ i don't see this @NobodyNo0ne

In the wiki:

Prerequisites

For larger changes, multiple changes and that may require adding new pages, it is strongly suggested to set up a local Jekyll instance. Please refer to Jekyll’s installation documentation to setup it up on your system. You will need to install ruby and gems.

Additionally, the theme will also need to be installed as the remote theme does not seem to work with locally severed Jekyll instances. Instructions for installing the Just the Docs theme can be found here.

So there is no direct link to docs for the theme.

That should be a seperate issue yes.

@tlaurion

tlaurion commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

Also, in the docs I have (still preliminary), I know flashprog is the better choice (at least I prefer it), but most distros package flashrom instead. I think Arch has flashprog?
Debian seems to have flashrom, Fedora seems to have flashrom, I have not checked other notable distros (like OpenSUSE package repos) yet. So its probably safer to assume a user reading the guide is using flashrom

also realised that heads won't default to 25.09 after this so I need to remove that note.

I'm not the best at writing, but everything that needs to be there, is there. I don't want to sit on this making small changes to how I have sentences written one by one.

Don't know how to do better then now

http://osresearch.net/SPI-Programmer-Best-Practices/#tool-interchangeability

We should not care nor repeat this in each board.

@tlaurion

Copy link
Copy Markdown
Collaborator

also realised that heads won't default to 25.09 after this so I need to remove that note

Yes, no version in docs. Otherwise a maintainership burden.

@tlaurion

Copy link
Copy Markdown
Collaborator

@tlaurion

Copy link
Copy Markdown
Collaborator

@NobodyNo0ne cleaned up things here see https://github.com/linuxboot/heads-wiki/compare/d536836393fab59e27aa48f9df1937c3faf98384..df863ae8141d9cfdce5d1d53b29ebba96c1de41b

Ok with that?

I have no clue why your github page doesn't update at:
https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/

Mine updated at:
https://tlaurion.github.io/heads-wiki/X280-maximized-flashing/

(writting typo should be corrected as can be seen per change preview in previous port, but is not in rendered in your page but is in mine per instructions for small github changes and config of github page)

@NobodyNo0ne

NobodyNo0ne commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

@NobodyNo0ne cleaned up things here see https://github.com/linuxboot/heads-wiki/compare/d536836393fab59e27aa48f9df1937c3faf98384..df863ae8141d9cfdce5d1d53b29ebba96c1de41b
Ok with that?

That cleanup is fine, I also see that it includes the PR for removing SPI speed mention. Sorry about the typos.

I have no clue why your github page doesn't update at: https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/

Mine updated at: https://tlaurion.github.io/heads-wiki/X280-maximized-flashing/

(writting typo should be corrected as can be seen per change preview in previous port, but is not in rendered in your page but is in mine per instructions for small github changes and config of github page)

I am fairly certain it is at /heads-wiki-x280/ because of the repo name. Now I unfortunately have no clue how to make it update after a change. I have not used github pages, and following the docs just feels like doing the same thing (going to settings -> pages -> deploy from branch -> try every option there is in the two dropdowns for branch and directory just to see if anything new happens) over and over until it eventually works. I no longer think CNAME affects it in any way.

I am surely doing something wrong, but from following the docs, I do not know what it would be. Best idea I have is that it just takes a while to update. Otherwise I have no clue.

@tlaurion

tlaurion commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

You can rebase + re-author here, its just that the 15 commits here we not needed and introduced typos too with many errors not related

@tlaurion

tlaurion commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

@NobodyNo0ne cleaned up things here see https://github.com/linuxboot/heads-wiki/compare/d536836393fab59e27aa48f9df1937c3faf98384..df863ae8141d9cfdce5d1d53b29ebba96c1de41b
Ok with that?

That cleanup is fine, I also see that it includes the PR for removing SPI speed mention. Sorry about the typos.

I have no clue why your github page doesn't update at: https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/
Mine updated at: https://tlaurion.github.io/heads-wiki/X280-maximized-flashing/
(writting typo should be corrected as can be seen per change preview in previous port, but is not in rendered in your page but is in mine per instructions for small github changes and config of github page)

I am fairly certain it is at /heads-wiki-x280/ because of the repo name. Now I unfortunately have no clue how to make it update after a change. I have not used github pages, and following the docs just feels like doing the same thing (going to settings -> pages -> deploy from branch -> try every option there is in the two dropdowns for branch and directory just to see if anything new happens) over and over until it eventually works. I no longer think CNAME affects it in any way.

I am surely doing something wrong, but from following the docs, I do not know what it would be. Best idea I have is that it just takes a while to update. Otherwise I have no clue.

it got updated meanwhile.

https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/ doesn't show previous "writting" typo: it's now gone.

@tlaurion

Copy link
Copy Markdown
Collaborator

@NobodyNo0ne cleaned up things here see https://github.com/linuxboot/heads-wiki/compare/d536836393fab59e27aa48f9df1937c3faf98384..df863ae8141d9cfdce5d1d53b29ebba96c1de41b
Ok with that?

That cleanup is fine, I also see that it includes the PR for removing SPI speed mention. Sorry about the typos.

I have no clue why your github page doesn't update at: https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/
Mine updated at: https://tlaurion.github.io/heads-wiki/X280-maximized-flashing/
(writting typo should be corrected as can be seen per change preview in previous port, but is not in rendered in your page but is in mine per instructions for small github changes and config of github page)

I am fairly certain it is at /heads-wiki-x280/ because of the repo name. Now I unfortunately have no clue how to make it update after a change. I have not used github pages, and following the docs just feels like doing the same thing (going to settings -> pages -> deploy from branch -> try every option there is in the two dropdowns for branch and directory just to see if anything new happens) over and over until it eventually works. I no longer think CNAME affects it in any way.

I am surely doing something wrong, but from following the docs, I do not know what it would be. Best idea I have is that it just takes a while to update. Otherwise I have no clue.

No change other then saying which branch its supposed to be rendering from + pushing new commit should be needed.

Can you scope the problem you encountered here?

Signed-off-by: NobodyNo0ne <akbarov2007@gmail.com>
@NobodyNo0ne

NobodyNo0ne commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

@NobodyNo0ne cleaned up things here see https://github.com/linuxboot/heads-wiki/compare/d536836393fab59e27aa48f9df1937c3faf98384..df863ae8141d9cfdce5d1d53b29ebba96c1de41b
Ok with that?

That cleanup is fine, I also see that it includes the PR for removing SPI speed mention. Sorry about the typos.

I have no clue why your github page doesn't update at: https://nobodyno0ne.github.io/heads-wiki-x280/X280-maximized-flashing/
Mine updated at: https://tlaurion.github.io/heads-wiki/X280-maximized-flashing/
(writting typo should be corrected as can be seen per change preview in previous port, but is not in rendered in your page but is in mine per instructions for small github changes and config of github page)

I am fairly certain it is at /heads-wiki-x280/ because of the repo name. Now I unfortunately have no clue how to make it update after a change. I have not used github pages, and following the docs just feels like doing the same thing (going to settings -> pages -> deploy from branch -> try every option there is in the two dropdowns for branch and directory just to see if anything new happens) over and over until it eventually works. I no longer think CNAME affects it in any way.
I am surely doing something wrong, but from following the docs, I do not know what it would be. Best idea I have is that it just takes a while to update. Otherwise I have no clue.

No change other then saying which branch its supposed to be rendering from + pushing new commit should be needed.

Can you scope the problem you encountered here?

I set Pages to deploy from the master branch, and folder /docs (I have also tried / (root) just to see if it changes anything. but I am fairly certain that is wrong.
Pushed a commit.
The build action shows success.
The site still shows old content.

I am thinking it might just take a while to update, even when the build says its fine. I just haven't seen mention of such a delay in the Heads wiki. <- I also do not see a way to force it to update the github page

@tlaurion
tlaurion merged commit aa9062a into linuxboot:master Sep 1, 2026
1 check passed
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

Successfully merging this pull request may close these issues.

2 participants