tlaurion
commented
11 months ago Open commandline-be opened 11 months ago
tlaurion
commented
11 months ago tlaurion
commented
11 months ago @commandline-be As said, nitrokey tested those changes at https://github.com/linuxboot/heads/pull/1522#issuecomment-1822489517 where https://github.com/linuxboot/heads/pull/1522/commits/e0fabb1534040f7571a9e60c5defdc75a47dba27 was added to have same removal of KERNEL_ADD paramameter (do not interfere with final OS grub configuration since unneeded) that nv41 was tested for at https://github.com/linuxboot/heads/pull/1522#issuecomment-1822543841
Basically what i'm saying is that now merged https://github.com/linuxboot/heads/pull/1522 might fix your issue. Again, not telling you to flash Heads master's now CircleCI produced rom under https://app.circleci.com/pipelines/github/linuxboot/heads/711/workflows/f16bc1d7-7246-4ffd-9a4c-2b54499eb4ae but this will land under NK 2.4 eventually with Nitrokey customizations on top of it after they thoroughly test it and decide its stable enough for themselves and their customers.
commandline-be
commented
11 months ago Looking forward to NK 2.4 I hope this also fixes #29 as that is really annoying.
tlaurion
commented
10 months ago As said earlier, base for 2.4 on heads is now considered tested and stable.
I would advise opening an issue so that nitrokey tracks coreboot changes as well and update both heads upstream and their fork to point to it and report upstream in coreboot fork any issue that won't be fixed here downstream unless reported and fixed upstream in coreboot fork.
That's how things work. :)
tlaurion
commented
10 months ago @jans23 I'm open to receive a donated nv41 and proper sporadic donations /monthly donations to help you with heads and coordinate needed work under coreboot fork.
But as of now, Heads upstream supports nitrokey boards as they are supported downstream. Issues flow upstream because unfixed downstream which is becoming a burden upstream.
You can contact me whenever you are ready to talk business.
commandline-be
commented
10 months ago As said earlier, base for 2.4 on heads is now considered tested and stable.
I would advise opening an issue so that nitrokey tracks coreboot changes as well and update both heads upstream and their fork to point to it and report upstream in coreboot fork any issue that won't be fixed here downstream unless reported and fixed upstream in coreboot fork.
That's how things work. :)
not going to push on this but i bought a laptop from NK and strictly speaking it doesn't perform as advertised i hope NK can concert future efforts better, this should be a much lower effort due to their approach and control over the HW
commandline-be
commented
10 months ago as expected, the overheating is not resolved by v2.4 since this is entirely due to heat generation and dissipation cooling down does go somewhat faster due to GPU taking some of the load now
tlaurion
commented
10 months ago @commandline-be some comparative quantitative measurements?
commandline-be
commented
10 months ago tlaurion
commented
10 months ago like this ? https://github.com/linuxboot/heads/issues/1551#issuecomment-1852533490
@commandline-be if compared with results after 2.4 it might help @daringer figure out, if any, kernel add parameters needed to be passed to OS per board config kexec call into final os, yes, summarizing here the before and after metrics.
commandline-be
commented
6 months ago fwiw, any heat issue are less noticeable with v2.4, I'm pretty sure the main reason is the nVME drive leading to the heat issues
Please identify some basic details to help process the report
A. Provide Hardware Details
1. What board are you using (see list of boards here)?
2. Does your computer have a dGPU or is it iGPU-only?
3. Who installed Heads on this computer?
4. What PGP key is being used?
5. Are you using the PGP key to provide HOTP verification?
B. Identify how the board was flashed
1. Is this problem related to updating heads or flashing it for the first time?
2. If the problem is related to an update, how did you attempt to apply the update?
3. How was Heads initially flashed
4. Was the board flashed with a maximized or non-maximized/legacy rom?
5. If Heads was externally flashed, was IFD unlocked?
C. Identify the rom related to this bug report
1. Did you download or build the rom at issue in this bug report?
2. If you downloaded your rom, where did you get it from?
Please provide the release number or otherwise identify the rom downloaded
3. If you built your rom, which repository:branch did you use?
4. What version of coreboot did you use in building?
5. In building the rom where did you get the blobs?
Please describe the problem
Describe the bug
This is notable for any version of the NV50 firmware (came installed with v2.2)
On multiple occassions the CPU temperature soars significantly (+30° C). On observation this seems highly likely to be related to the nvme storage which seems to suffer on repeat, infrequent disk writes(?) other specific patterns.
Multiple reproducible software were found such as but not limited to: suricata, mailspring (daemon)
To Reproduce Steps to reproduce the behavior: (suricata)
Expected behavior much less impact on the CPU when using the nvme storage
Screenshots possible but not provided at this time
Additional context the particular nvme shows impairment to specific workloads it is likley the firmware is not optimally configured to work with this nvme recommendation is to switch to nvme which do not depend on CPU or correct configuration issue(s)