i thought “oh this may activate my on screen keyboard automatically, since it doesnt work on gnome properly”
it disabled the keyboard
i rebooted since i thought that would fix it
now i cant enter my password for the full disk encryption because it is in the shell and not a gui app
i cant enter bios because the keyboard is disabled so i cant boot off a usb and fix this
i am really stupid
as I was typing this I realized that external keyboard would probably fix this and it did, however I think it’s a huge oversight on the part of framework, to disable the keyboard completely even for bios
@zenmaya I hope you are enjoying your new laptop! I just got one myself as well.
You should be able to reset this state by doing the following.
Power the system off. you can do this by holding down the power button for about 15-30 seconds to force shutdown.
Unplug all chargers.
Wait 2 minutes.
Power the system back on.
framework_tool is more of an engineering/debug tool, but lots of users use it to customize their system behavior to their liking.
I suppose what is a brick, and how badly bricked depends on the person. If it’s not usable at all to you, does it matter how easy to return to functionality for a different person? Still a brick for you unless or until a solution is found. And there is a level of panic when something expensive stops working in a fundamental way.
(We can leave a person’s state of mind out of the definition)
Let’s take an example of a broken display panel, no display until you plug in an external display. You don’t classify that as a brick. You’ve spilled water onto the keyboard, keyboard isn’t working, that’s not a brick.
Well after all, doesn’t the term brick inherently come with qualifications not far off that?
I can brick my phone dead to me, and the majority of people, but to someone with the right knowledge and equipment at hand it might be nothing but a moment’s inconvenience. Would still be dead to me. Do I care that it’s not a problem to someone else?
It’s just good that in this case it turned out not as bad as it might have initially seemed.
It’s actually quite far off. Brick is typically related to firmware or hardware level start up process that can’t even complete. Regardless of OS / software / configuration.
In the case of OP, it was a configuration change without sufficient warning and / or detailed to end user. The hardware started, no firmware corruption.
e.g. Bad RAM module prevented mainboard start up, not a brick. GRUB missing, can’t boot OS, not a brick. Touchpad not working, not a brick. CPU dead, it’s a brick. Corrupted BIOS, it’s a brick.
If the external keyboard and no other input device had worked, but it was recoverable (e.g. config reset procedure of some sorts)…then that’s a soft brick.
OP’s external keyboard worked, no reset was needed to revert the configuration, not even a brick.
Maybe it’s more about just reconsidering policing someone’s word choice. And a new member of the forum as well. Not the most pleasant welcome. I’ve edited my original post. But either way, no need for us to continue to debate it in their thread.
However you want to frame it, it was inaccurate use of the word for dramatic thread title. (“I’m going to catch a truck.” “Don’t you mean a bus” “No, it’s a truck, has space, carry many things, on many wheels” “No, that’s a bus”)
Glad it’s not bricked. (Note: I’m not saying you or the OP can’t continue to call it a brick. I’m not asking anyone to [not] say / use any words they want. I’m saying that’s not what happened.)