7dev7random7

joined 10 months ago
[–] [email protected] 3 points 2 months ago (1 children)

Thank you for your kind words and objective perspective.

[–] [email protected] 1 points 2 months ago

Indeed it is. Though I just started to leverage its capabilities.

Nonetheless, I would again buy into aarch64.

[–] [email protected] 3 points 2 months ago

I will be more sensible the next time and I took my lesson. Thank you for elaborating clearly!

[–] [email protected] 1 points 2 months ago (1 children)

I don't see myself like this but thanks for your analysis.

[–] [email protected] 1 points 2 months ago

I paid 1200 EUR.

[–] [email protected] 1 points 3 months ago

You may chime in here: I purchased it with three years of support as well (they [Lenovo] exchanged my brickes speakers, btw).

[–] [email protected] 3 points 3 months ago (1 children)

Thank you for your persistance. Edited it, Sir or Madame.

[–] [email protected] 1 points 3 months ago (1 children)

You are untinted. Tha nk 's for th is, bot.

[–] [email protected] 3 points 3 months ago* (last edited 3 months ago) (3 children)

I edited both:

[–] [email protected] 7 points 3 months ago (4 children)

The listing price was $2700 on purchase. I bought it for around $1800. The $650 dollar are from the Lenovo outlet store. I could sell this laptop for less then $500 on ebay.

[–] [email protected] 7 points 3 months ago

More insights I gained using this laptop (intended for the curious Linux enthusiast):

  • Kernel support for Audio and Screens is heavily dependend on user space: X.org and Wayland experience differs immensely. Even some udev-rules only work with certain compositors (and X11 feels like it is out of scope).
  • Debian lacks people contributing to the linux and linux-firmware package. The onboarding is quite steep due to a lack of alignment between code and documentation.
  • Developers if userspace programs react very fast to new requirements but they rely on upstreamed (to Debian's kernel-team) kernel-config's.
  • Prompting bugs to the kernel appears to be done through kernel contributors only: Users will prompt hindrances on IRC (via OTFC, #aarch64-laptops) prompting the contributor and they will verify and support before addressing issues.
  • There are archived advancements to the support which can't be merged due to citation reasons and alignment with upstream can't be done by the individual (there is a pareto-capable kernel for virtualization but within one week hunderts of commits need to get reviewed). This is impressive imo.
view more: ‹ prev next ›