System76

Searching online, for general keycaps, the recommendation is to soak them in soapy water for an hour. I am assuming that is fine here, but wanted to double check if that is indeed the case. Thanks!

Recently I noticed my Lemur Pro wasn't closing up neatly, and the click action of the touchpad had become quite difficult. When I griped about this, somebody said check and see if your battery is swollen. But this machine is barely over a year old. The battery should be fine, right? Batteries in my other laptops (which have all been Macs) lasted years.

As soon as I looked, the bulging of the keyboard and the bottom of the case was obvious. Not sure how I hadn't already noticed it. I found a replacement battery online, though getting the old "spicy pillow" out was a bit of a nuisance. It was pretty firmly glued in.

Why did the battery fail so soon? I always noticed the Lemur Pro was warm when running and, oddly, stayed warm when I had it closed up and suspended. Heat is not good for a battery. Why was it warm when suspended? Well, I just assumed it's a kind of a crummy design and that's just how they all are.

TODAY when I was poking around in System Settings (in Mint Cinnamon, which is what I run on both the Lemur Pro and my Thelio now), I discovered that there are Power Management settings for this, and that I had mine set to never suspend when it was plugged in, even if the case was closed.

Honestly, it had never crossed my mind that there were settings for this. I just assumed it was like those Macs I had before, and they all suspended when they were closed. I usually didn't shut them down, but just habitually left them plugged in and closed up all the time when I wasn't using them, and they were fine. I guess I had my Lemur Pro sitting there idling (but not suspended) and staying warm almost continuously for the past year, and the battery couldn't take that.

Lesson learned. Check your power management settings, especially if you come in from a platform that might work differently.

The fan speed curve on the Oryx Pro is wild. It seems to have basically two speeds: jet engine takeoff and dead silent. Is there a way to control this better that doesn't involve editing firmware? I see some posts from earlier this year on this topic but wondering if the situation has evolved — I don't really want to do something that won't be well-supported.

I'm in Canada, bought it with the corresponding (US) power supply, just received it, plugged it into a wall outlet, made sure the power supply is on... And when I turn it on, it shuts off before even fully booting. Not at any specific point in booting, either, it just seems like the power cuts off. Sometimes, if I turn it back on soon after, it barely stays on for two seconds. Tried a different outlet with the same result. Nothing else seems out of the ordinary, fans are a bit loud, but not so much that it seems strange for a booting computer.

Made a support ticket but it seems like service may be slow until Monday. Anyone ever experienced something like this?

So I'm looking for a Linux laptop to replace my trusty old 2013 Macbook Pro which is now EOL. I could use some faster hardware anyway. I looked at the Adder, and it seems like it has almost everything I want. Open firmware, good documentation, etc. However there's just one little thing...

The display. My MBP has a 2560x1440 display and I love it because when I'm coding in CLion, Intellij or whatnot I have lots of screen real estate. But the Adder only goes up to 1080p. I could go all the way up to a Bonobo, but I really don't want to lug around a 17" laptop anymore. I'm getting old.

So, my question is this... anyone moved from a Retina display back down to 1080p and had major problems with it? Any fellow coders miss the extra screen real estate? Or am I worrying over nothing?

I received and installed a brand new Thelio. I was unable to get it to resume after suspend. I see some posts about this issue, but no definite resolution. Does anyone know of a fix for this? If I disable suspend in the Pop system settings, will that help and what is the impact, it is the machine never going to sleep?

Hi guys,

wanted to ask here before I open a ticket in S76 desk, I just wanted to ask you guys about this issue. I just got myself a brand new Gazelle laptop this July and it has worked fine up until now.

This morning I started up my laptop and disconnected the power cord, using only battery power. I was doing some other stuff for a couple of hours and left my laptop on the table without the power cord and when I looked at my laptop again, it was all blacked out and won't start anymore. I plugged the power cord back on, but pressing the power button does nothing. I can see the yellow light coming from charging the battery. I have taken good care of my laptop, not poured any liquids on it or anything. But it just stopped working.

I just wanted to get your tips and pointers as to what to do. Is there like a hard reset button or should I open up the case and disconnect the battery? Anything else I could try out, other than waiting for a couple of days and hoping it starts working again?

I will accept any used System76 device.

I will accept any used System76 device.

Just an FYI, that something seems to be amiss with Kernel 6.6.

I run OpenSUSE Tumbleweed on my Darter Pro.

I've found that, starting with early kernel 6.6 releases (and up to at least 6.6.1) the path '/sys/class/leds/system76_acpi::kbd_backlight` no longer exists, and the keyboard backlight is no longer controllable (and defaults to off). Kernel 6.5.9 is the most recent version I've found that works.

There are no relevant kernel configuration changes that I can see between then and now, as packaged by opensuse.

The following is in my dmesg buffer post-boot on this 6.6.1 kernel:

[   16.203995] sysfs: cannot create duplicate filename '/devices/LNXSYSTM:00/LNXSYBUS:00/17761776:00/leds/system76_acpi::kbd_backlight/color'
[   16.204003] CPU: 0 PID: 1232 Comm: (udev-worker) Not tainted 6.6.1-1-default #1 openSUSE Tumbleweed 0c6504f7d2c054731662677f280b3e0e68eca996
[   16.204007] Hardware name: System76 Darter Pro/Darter Pro, BIOS 2022-11-21_b337ac6 11/14/2022
[   16.204009] Call Trace:
[   16.204012]  
[   16.204015]  dump_stack_lvl+0x47/0x60
[   16.204023]  sysfs_warn_dup+0x5a/0x70
[   16.204028]  sysfs_add_file_mode_ns+0x11a/0x130
[   16.204031]  internal_create_group+0x115/0x3a0
[   16.204035]  internal_create_groups+0x42/0xa0
[   16.204038]  device_add+0x597/0x890
[   16.204042]  ? kstrdup+0x4c/0x70
[   16.204045]  device_create_groups_vargs+0xce/0xf0
[   16.204049]  device_create_with_groups+0x43/0x60
[   16.204053]  led_classdev_register_ext+0x1c1/0x430
[   16.204057]  ? devm_led_classdev_register_ext+0x3a/0x90
[   16.204060]  ? __pfx_devm_led_classdev_release+0x10/0x10
[   16.204063]  devm_led_classdev_register_ext+0x50/0x90
[   16.204066]  system76_add+0x18b/0x440 [system76_acpi 6778ab907a326eeb6d97e8c957cf2c7d3aa12d04]
[   16.204074]  ? sysfs_do_create_link_sd+0x6e/0xe0
[   16.204077]  acpi_device_probe+0x47/0x130
[   16.204082]  really_probe+0x19b/0x3e0
[   16.204085]  ? __pfx___driver_attach+0x10/0x10
[   16.204088]  __driver_probe_device+0x78/0x160
[   16.204090]  driver_probe_device+0x1f/0x90
[   16.204093]  __driver_attach+0xd2/0x1c0
[   16.204095]  bus_for_each_dev+0x74/0xc0
[   16.204096] input: PC Speaker as /devices/platform/pcspkr/input/input9
[   16.204097]  bus_add_driver+0x116/0x220
[   16.204100]  driver_register+0x59/0x100
[   16.204103]  ? __pfx_system76_driver_init+0x10/0x10 [system76_acpi 6778ab907a326eeb6d97e8c957cf2c7d3aa12d04]
[   16.204109]  do_one_initcall+0x47/0x310
[   16.204114]  ? kmalloc_trace+0x2a/0xa0
[   16.204117]  do_init_module+0x60/0x240
[   16.204121]  __do_sys_init_module+0x17f/0x1b0
[   16.204125]  ? __seccomp_filter+0x31b/0x510
[   16.204129]  do_syscall_64+0x5d/0x90
[   16.204132]  ? do_syscall_64+0x6c/0x90
[   16.204134]  ? do_syscall_64+0x6c/0x90
[   16.204136]  ? do_user_addr_fault+0x30f/0x660
[   16.204140]  ? exc_page_fault+0x71/0x160
[   16.204143]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[   16.204147] RIP: 0033:0x7f7e7ed199de
[   16.204163] Code: c3 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 12 14 0d 00 f7 d8 64 89 01 48
[   16.204165] RSP: 002b:00007fff7a559488 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[   16.204169] RAX: ffffffffffffffda RBX: 000055a52271d0b0 RCX: 00007f7e7ed199de
[   16.204170] RDX: 00007f7e7f41c061 RSI: 0000000000008323 RDI: 00007f7e7e406010
[   16.204172] RBP: 00007f7e7f41c061 R08: 0000000000000630 R09: 0000000000000000
[   16.204173] R10: 00007f7e7edebb20 R11: 0000000000000246 R12: 0000000000020000
[   16.204175] R13: 0000000000000000 R14: 000055a52271f950 R15: 0000000000000000
[   16.204177]  
[   16.204208] System76 ACPI Driver: probe of 17761776:00 failed with error -17

Just an FYI, that something seems to be amiss with Kernel 6.6.

I run OpenSUSE Tumbleweed on my Darter Pro.

I've found that, starting with early kernel 6.6 releases (and up to at least 6.6.1) the path '/sys/class/leds/system76_acpi::kbd_backlight` no longer exists, and the keyboard backlight is no longer controllable (and defaults to off). Kernel 6.5.9 is the most recent version I've found that works.

There are no relevant kernel configuration changes that I can see between then and now, as packaged by opensuse.

The following is in my dmesg buffer post-boot on this 6.6.1 kernel:

[   16.203995] sysfs: cannot create duplicate filename '/devices/LNXSYSTM:00/LNXSYBUS:00/17761776:00/leds/system76_acpi::kbd_backlight/color'
[   16.204003] CPU: 0 PID: 1232 Comm: (udev-worker) Not tainted 6.6.1-1-default #1 openSUSE Tumbleweed 0c6504f7d2c054731662677f280b3e0e68eca996
[   16.204007] Hardware name: System76 Darter Pro/Darter Pro, BIOS 2022-11-21_b337ac6 11/14/2022
[   16.204009] Call Trace:
[   16.204012]  
[   16.204015]  dump_stack_lvl+0x47/0x60
[   16.204023]  sysfs_warn_dup+0x5a/0x70
[   16.204028]  sysfs_add_file_mode_ns+0x11a/0x130
[   16.204031]  internal_create_group+0x115/0x3a0
[   16.204035]  internal_create_groups+0x42/0xa0
[   16.204038]  device_add+0x597/0x890
[   16.204042]  ? kstrdup+0x4c/0x70
[   16.204045]  device_create_groups_vargs+0xce/0xf0
[   16.204049]  device_create_with_groups+0x43/0x60
[   16.204053]  led_classdev_register_ext+0x1c1/0x430
[   16.204057]  ? devm_led_classdev_register_ext+0x3a/0x90
[   16.204060]  ? __pfx_devm_led_classdev_release+0x10/0x10
[   16.204063]  devm_led_classdev_register_ext+0x50/0x90
[   16.204066]  system76_add+0x18b/0x440 [system76_acpi 6778ab907a326eeb6d97e8c957cf2c7d3aa12d04]
[   16.204074]  ? sysfs_do_create_link_sd+0x6e/0xe0
[   16.204077]  acpi_device_probe+0x47/0x130
[   16.204082]  really_probe+0x19b/0x3e0
[   16.204085]  ? __pfx___driver_attach+0x10/0x10
[   16.204088]  __driver_probe_device+0x78/0x160
[   16.204090]  driver_probe_device+0x1f/0x90
[   16.204093]  __driver_attach+0xd2/0x1c0
[   16.204095]  bus_for_each_dev+0x74/0xc0
[   16.204096] input: PC Speaker as /devices/platform/pcspkr/input/input9
[   16.204097]  bus_add_driver+0x116/0x220
[   16.204100]  driver_register+0x59/0x100
[   16.204103]  ? __pfx_system76_driver_init+0x10/0x10 [system76_acpi 6778ab907a326eeb6d97e8c957cf2c7d3aa12d04]
[   16.204109]  do_one_initcall+0x47/0x310
[   16.204114]  ? kmalloc_trace+0x2a/0xa0
[   16.204117]  do_init_module+0x60/0x240
[   16.204121]  __do_sys_init_module+0x17f/0x1b0
[   16.204125]  ? __seccomp_filter+0x31b/0x510
[   16.204129]  do_syscall_64+0x5d/0x90
[   16.204132]  ? do_syscall_64+0x6c/0x90
[   16.204134]  ? do_syscall_64+0x6c/0x90
[   16.204136]  ? do_user_addr_fault+0x30f/0x660
[   16.204140]  ? exc_page_fault+0x71/0x160
[   16.204143]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[   16.204147] RIP: 0033:0x7f7e7ed199de
[   16.204163] Code: c3 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 12 14 0d 00 f7 d8 64 89 01 48
[   16.204165] RSP: 002b:00007fff7a559488 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[   16.204169] RAX: ffffffffffffffda RBX: 000055a52271d0b0 RCX: 00007f7e7ed199de
[   16.204170] RDX: 00007f7e7f41c061 RSI: 0000000000008323 RDI: 00007f7e7e406010
[   16.204172] RBP: 00007f7e7f41c061 R08: 0000000000000630 R09: 0000000000000000
[   16.204173] R10: 00007f7e7edebb20 R11: 0000000000000246 R12: 0000000000020000
[   16.204175] R13: 0000000000000000 R14: 000055a52271f950 R15: 0000000000000000
[   16.204177]  
[   16.204208] System76 ACPI Driver: probe of 17761776:00 failed with error -17

I have a gaze15 and I took it apart to clean and after none of the drives would show up. I started messing with bios and it's worse now. Also how do I find pop os kernel?

https://preview.redd.it/hxquxujyna1c1.jpg?width=8160&format=pjpg&auto=webp&s=44fdbbe678884d996d6a20ab59fae07a994a19ac

https://preview.redd.it/qb67htxzna1c1.jpg?width=8160&format=pjpg&auto=webp&s=7bf2446e629dccb1aa7f13280fc7bdc3d1881b9d

I received my laptop today in the mail. Upon booting it up for the first time I noticed the touchpad is unresponsive.

I tried disabling and renabling the touchpad via the FN+F1 keyboard shortcut to no avail. I also tried both the default Pop_os as well as the most recent stable version of Ubuntu to the same result.

Plugging in an external mouse works fine however.

​

Has anyone else ran into this issue?

This one: https://www.microcenter.com/product/660428/samsung-990-pro-1tb-samsung-v-nand-3-bit-mlc-pcie-gen-4-x4-nvme-m2-internal-ssd

Reason why I ask is because the lemur Manuel says PCIe NVMe Generation 3, and the one I’m trying to buy is Gen 4?

Any help is appreciated.

I saw on at my friend's house and it looks good he was gatekeeping it tho

Hello everyone, I'm considering the Lemur Pro for its combination of lightweight design and long battery life workstation. However, I'm a bit concerned about its build quality. I've come across some posts from 1-2 years ago suggesting that the build quality might not be the best. Have there been any improvements or updates in this area or still the same?

Just got a new Thelio Spark. When I pulled it out of the box I heard something moving around. I opened the case to see if I could isolate it. There's a metal enclosed compartment inside the case, and something is sliding around in there. I think I can see heat sinks and the word "Antec." I'd have to get into that compartment to describe it further.

I've pinged support and I'm hoping it's a self repair. It must be the fan? How do those things attach inside that compartment?

​

https://preview.redd.it/4hq2hdkj980c1.png?width=1915&format=png&auto=webp&s=7671f80137ef34c73de0f039fa99829ef8fba2f0

I bought my first machine from them around 5 years ago. I was extremely impressed with their support after assisting me multiple times with issues that weren't directly related to S76.

I now have a new Darter Pro 9 and having issues with the Thunderbolt port and eGPU which I believe to be a hardware failure. However, I have created 3 tickets with them now and just sat on hold for 15 minutes before getting dropped to voicemail which I don't have much confidence that I'll be getting a call back.

​

Before, their response was extremely fast, friendly and ususally could solve my issues. Now I can't even get a timely response. Starting to second guess my purchase, but can't even get in touch with them to do anything about it.

I do not have much to say; I just think System76 does good work. I really appreciate the technical support (the few times I've needed it). I very very much look forward to when they release their own laptops (instead of Clevo which, to be honest, are fine).

I have a Lemur Pro (9) and the damned thing just works. Non-stop.

Keep up the good work, folks. I don't expect perfection, but what you have been doing is very very good. And your friendliness to right-to-repair pushes me to being a loyal S76 customer.