You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was contacted today by ns70 owner having Heads when platform was received and was asked to be paid to support that user.
Doing 1:1 support won't help ecosystem. Clarify HCL and compatibility for ns70 with ns50 under Heads tree is needed if ns70 was sold by Nitrokey and therefore Heads, which I was unaware up to today.
tlaurion
changed the title
ns70 being supported or not supported by ns50 under Dasharo coreboot fork?
ns70 being supported or not supported by ns50 under Dasharo coreboot fork, then Heads by Nitrokey fork and support?
Jan 15, 2025
I was contacted today by ns70 owner having Heads when platform was received and was asked to be paid to support that user.
Doing 1:1 support won't help ecosystem. Clarify HCL and compatibility for ns70 with ns50 under Heads tree is needed if ns70 was sold by Nitrokey and therefore Heads, which I was unaware up to today.
If I'm the one trying to get help, as the release change log says V2.4 NS70 is supported on NS50.
In support they tell me that they do not help to do a reflashing, except that I must pay (150 euros + shipping) and send the laptop to Germany, what is cumbersome and cost is also contrary to the company's policies. I saw a similar situation in the official forum a user needed help but they answered with the typical answer "1: 1"
So I seek help in exchange for a reward. Unlike Nitrokey, Novacustom and Dasharo if you have a good support for this type of situation.
This is to track ns50 HCL support.
I was contacted today by ns70 owner having Heads when platform was received and was asked to be paid to support that user.
Doing 1:1 support won't help ecosystem. Clarify HCL and compatibility for ns70 with ns50 under Heads tree is needed if ns70 was sold by Nitrokey and therefore Heads, which I was unaware up to today.
@daringer ?
The text was updated successfully, but these errors were encountered: