linux-surface VS linux

Apart from camera, almost everything is working correctly. Camera doesn't work at all.

https://github.com/linux-surface/linux-surface

I use this kernel, you can use this with most operating systems.

I use xournal++ for note writing, and using GNOME is necessary. KDE doesn't have support for screen rotation etc. When you use GNOME, make sure to disable gestures and screen edge detection, because that might occasionally cause problems.

So, the workflow is quite simple with xournal++, you run a `inotify` based watched which automatically compiles and pushes stuff on every save. I of course assume that only `xournal++` on tab can change those handwritten notes. You can get some fancier git logic if needed.

```

while inotifywait -e modify,create,delete,move $INPUT;

There's support for Linux on the Surface range:

https://github.com/linux-surface/linux-surface/wiki/Supporte...

But actual users seem to say it's a bit of a mixed bag.

If someone's looking for a laptop (that doesn't need touchscreen support), then Apple laptops are probably the better choice.

How to get out of this situation? Links https://github.com/linux-surface/linux-surface/issues/1240 - the same problem as I have and the same puncture, but the person managed to get out of the situation https://www.reddit.com/r/SurfaceLinux/comments/16d40vs/kill_my_surface_pro_2017_need_help/ - my similar post in a nearby subreddit, but since I'm here, the problem turned out to be bigger than I thought

https://github.com/linux-surface/linux-surface

Should have you covered.

I went the 12” MacBook route which can also install Linux.

I have a surface with Ubuntu and the Surface Kernel (https://github.com/linux-surface/linux-surface) , and it works really wonderfully. I will say, before installing the Surface Kernel, it was very janky.

I know about https://github.com/linux-surface/linux-surface but I'm looking for practical feedback from people who did the operation in order to orient my choice.

3.x support will come to toltec, I've been blocked by stuff outside of my control a couple of times. Including things happening in my life that I won't get into.

You can see the current progress here: https://github.com/toltec-dev/toltec/issues/820

As for the comment on the kernel change, that was actually an ask by someone in the community: https://github.com/reMarkable/linux/issues/8

Did anyone already ask reMarkable for a copy of the source code for those kernel modules, which should be possible according to the GPLv2? Their kernel repo on GitHub does not seem to be updated yet.

The official linux kernel documentation of the power_supply class is located here. If you read that you may notice there are some lines in the uevent file that aren't described. That's because the particular battery has other statistics exposed by the driver (source file here). Looking at the source file (and datasheet of the MAX77818), it appears that the CURRENT_NOW is a measurement of the current going in/out of the battery. It's stored as a signed number so the negative value you're seeing is probably the current flowing out of the battery while it's discharging. The CURRENT_AVG is simply an average of the CURRENT_NOW over a time period, so it will stay negative for a little while if you just plugged in the charger, before settling to 0.

[1] https://github.com/reMarkable/linux/pull/12

Remarkable uses openembedded, the kernel source can be found here https://github.com/reMarkable/linux only the user facing gui software is closed source and there are launchers that can start other gui programs. There is also a framework somewhere on githuvlb for writing native gui apps and so on. There is also the project http://www.davisr.me/projects/parabola-rm/ that provide an alternative os.

This line seems like the obvious cry for help from the driver. This is the file responsible for the error (I think): https://github.com/reMarkable/linux/blob/lars/zero-gravitas_4.9/drivers/input/touchscreen/wacom_i2c.c but unfortunately I haven't found out anything useful.