I was just reading this message, which mentions that a motherboard reset procedure for Framework 16 motherboard is unknown. While I vaguely recall another user mentioning a procedure that worked for them to reset a Framework 16 motherboard. (Edit: found it at the start of here)
So I want to put forward a suggestion for Framework to bring up a Wiki-style site where users can create and edit a knowledge base.
Should lighten the support burden and create a centralized place for all the extended knowledge shared with and by the community.
And it would be more search-engine friendly than the forum. And could also be the place where Framework themselves publish stuff like pinouts, etc.
It’s kind of bare bones. We should have a page about like, reset button, driver, etc.
I think the site organization make more sense if we organize by category rather than device. We only have two (device). If we are to add everything about them in 1 page it gets rather lengthy.
Feel free to add it! That’s the point of a wiki!
(I only have so much time, between work, being a full-time student, and moderating the Framework community. It’s a community effort – if you have things to improve, please do so!)
It’s broken down into device category, and then into individual generations. See the Framework Laptop 13 pages – the 16" page is in a weird spot because there’s only one generation at the moment. It’s set up this way so the site can expand as Framework does without needing major reorganization.
There can be multiple pages about different aspects of a given generation (as long as they’re long enough to justify it – stubs should be kept to a minimum and may get merged into a different page), but I want to keep the site organized by device. Even just within different generations of Framework Laptop 13, many resources and guides for one generation don’t work for others, and that gets quite complicated to manage with any other organizational system.
So if I am to add, say, CMOS reset, I should put them under each gen of each computer?
I was going to move the framework-16 content into its own folder, expecting future generations with modifications. Except I can’t clone the repo and I got
error: invalid path 'wiki/framewiki:citation-needed.md'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
Since it differs by generation, I think that would be the best way to go about it.
I would need to see more of the logs than this, including the commands you ran. Did you fork the repo first, or are you attempting to work on the main repo which you would not have write access to?
Either way, I’d prefer to keep the 16” page without a folder unless/until Framework releases a new generation.
I was cloning it to desktop, via the github desktop app
I guess we can always just move the page.
My point is, something like the BIOS blink code. Is pretty much universal across all the devices. The 13, and the 16. So that I feel like should just live on its own separate page, rather than being duplicated across all the machines.
And the BIOS reset, seems to be universal across all 13s
The BIOS reset procedure is different between different models. 11th gen and 12th gen (and possibly 13th gen) use different instructions than core ultra 1 and AMD. The applicable instructions either need to be on each page, or a page for the instructions that is broken down by model. I would probably opt for the latter, probably under a top-level “guides” page.
I believe the port80 codes are the same between models, but I’ve seen no official confirmation of that fact. If it can be verified, then it would make sense to create a dedicated page for it.
You need to fork the repo to your GitHub account before cloning it to local and checking out a branch. You should be able to do everything you need to from the browser though, as outlined in the contributing instructions.
Interesting! I’ll look into changing those file names then – shouldn’t cause much of an issue for normal editors though, as everything is markdown (unless you’re doing actual dev work, most of which is in a separate repo) which can be edited using either GitHub’s web editor or github.dev for bigger organizational edits.
It looks like it’s expired and pending deletion now, according to whois data. (As an aside: I looked at registering that one, but it was already registered when I purchased the domain. I probably wouldn’t have registered it anyway, given it’s legally questionable to use a domain name that includes a company’s full trademarked name without being affiliated with them.)
I think it would be good to have a wiki that anyone can edit.
I looked at https://framewiki.net/
but it won’t let me edit any of the pages.
For example,
There are a few threads that mention BIOS code 0xC5 when a AMD FW13 or FW16 will not boot.
It looks like the problem is related to a RAM slow. (not the RAM chip, the slot itself).
It seems that a fix in all the cases I have seen on here has been to replace the Mainboard.
I though I might be a good idea to capture this troubleshooting on a Wiki page.
We don’t know what the BIOS is doing when it outputs a 0xC5, but we do at least know what the fix is.
@Morpheus636
Yes, but really, forking the code and then changing it there etc. etc. is not exactly in the spirit of a wiki where you can just edit what is there in place.
Its enough of a hurdle for me not to bother contributing, I don’t know about others.
