Literally 2 years passed since that CPUs out of there, note thay Apple silicon now has a proper and BETTER support than this Snapdragons, they said "we gonna make Native Linux support" and we still waiting. I was planning to get great Linux laptop with great battery and performance thans to Snapdragon, now its impossible. Only usable OS option out there is Ubuntu and its NOT good too, there is still some issues on Audio, performance is worst than Intel 12th gen i5, battery time worst than Windows, i dont understand. Am i wrong or something? What they promised what they said and what they doing, propiertary driver. When we will get proper Linux support, or this devices gonna get burried with Windows

Hello r/linux,

I'm a developer working on accessibility software, specifically a cross-platform dwell clicker for people who cannot physically click a mouse. This tool is critical for users with certain motor disabilities who can move a cursor but cannot perform clicking actions.

How I Personally Navigate Computers

My own computer usage depends entirely on assistive technology:

• I use a Quha Zono 2 (a gyroscopic air mouse) to move the cursor
• My dwell clicker software simulates mouse clicks when I hold the cursor still
• I rely on an on-screen keyboard for all text input

This combination allows me to use computers without traditional mouse clicks or keyboard input. XLib provides the crucial functionality that makes this possible by allowing software to capture mouse location and programmatically send keyboard and mouse inputs. It also allows me to also get the cursor position and other visual feedback. If you want an example of how this is done, pyautogui has a nice class that demonstrates this.

The Issue with Wayland

While I've successfully implemented this accessibility tool on Windows, MacOS, and X11-based Linux, Wayland has presented significant barriers that effectively make it unusable for this type of assistive technology.

The primary issues I've encountered include:

• Wayland's security model restricts programmatic input simulation, which is essential for assistive technologies
• Unlike X11, there's no standardized way to inject mouse events system-wide
• The fragmentation across different Wayland compositors means any solution would need separate implementations for GNOME, KDE, etc.
• The lack of consistent APIs for accessibility tools creates a prohibitive development environment
• Wayland doesn't even have a quality on-screen keyboard yet, forcing me to use X11's "onboard" in a VM for testing

Why This Matters

For users who rely on assistive technologies like me, this effectively means Wayland-based distributions become inaccessible. While I understand the security benefits of Wayland's approach, the lack of consideration for accessibility use cases creates a significant barrier for disabled users in the Linux ecosystem.

The Hard Truth

I developed this program specifically to finally make the switch to Linux myself, but I've hit a wall with Wayland. If Wayland truly is the future of Linux, then nobody who relies on assistive technology will be able to use Linux as they want—if at all.

The reality is that creating quality accessible programs for Wayland will likely become nonexistent or prohibitively expensive, which is exactly what I'm trying to fight against with my open-source work. I always thought Linux was the gold standard for customization and accessibility, but this experience has seriously challenged that belief.

Does the community have any solutions, or is Linux abandoning users with accessibility needs in its push toward Wayland?

Hey everyone,

I’ve been diving deep into the early days of Linux and decided to implement a functional (albeit primitive) GUI on top of Linux 0.11. My main goal was to understand the interaction between kernel interrupts and framebuffer rendering in a vintage environment.

Technical Implementation:

VGA Driver: Developed a custom driver to handle 640x480 resolution (16-color mode) by writing directly to VGA registers.

Window Manager: Built a lightweight windowing system that supports basic movement and stacking logic.

Event Handling: Integrated PS/2 mouse support and keyboard interrupts. The GUI processes these events through a custom event loop integrated into the kernel.

Graphics Library: Implemented a primitive rendering engine for drawing pixels, lines, and rectangles directly to the frame buffer.

The Choice of 0.11:

I chose version 0.11 because its codebase is compact enough to be fully understood, yet it provides a "real" Unix-like environment. Managing memory and task switching while pushing pixels has been an incredible low-level engineering challenge.

Current Roadmap:

Optimization: Improving the redraw logic to eliminate flickering (implementing a back-buffer).

Applications: Porting a basic text editor to run within the window manager.

Kernel Stability: Refining interrupt handling for smoother mouse movement.

Note: This is an ongoing project focused on OS development and learning the fundamentals of early Linux architecture

Recently, just before Christmas, I decided to check out Linux again (tried it ~20 years ago) because Windows 11 was about to cause an aneurysm.

I was expecting to spend the "weekend" getting everything to work; find hardware drivers, installing various open source software and generally just 'hack together something that works'.

To my surprise everything worked flawlessly first time booting up. I had WiFi, sound, usb, webcam, memory card reader, correct screen resolution. I even got battery status and management! It even came with a nice litte 'app center' making installation of a bunch of software as simple as a click!

And I remember thinking any Windows user could easily install Linux and would get comfortable using it in an afternoon.

I'm pretty 'comfortable' in anything PC and have changed boot orders and created bootable things since the early 90's and considered that part of the installation the easiest part.

However, most people have never heard about any of them, and that makes the two steps seem 'impossible'.

I recently convinced a friend of mine, who also couldn't stand Window11, to install Linux instead as it would easily cover all his PC needs.

And while he is definitely in the upper half of people in terms of 'tech savvyness', both those "two easy first steps" made it virtually impossible for him to install it.

He easily managed downloading the .iso, but turning that iso into a bootable USB-stick turned out to be too difficult. But after guiding him over the phone he was able to create it.

But he wasn't able to get into bios despite all my attempts explaining what button to push and when

Next day he came over with his laptop. And just out of reflex I just started smashing the F2 key (or whatever it was) repeatingly and got right into bios where I enabled USB boot and put it at the top at the sequence.

After that he managed to install Linux just fine without my supervision.

But it made me realise that the two first steps in installing Linux, that are second nature to me and probably everyone involved with Linux from people just using it to people working on huge distributions, makes them virtually impossible for most people to install it.

I don't know enough about programming to know of this is possible:

Instead of an .iso file for download some sort of .exe file can be downloaded that is able to create a bootable USB-stick and change the boot order?

That would 'open up' Linux to significantly more people, probably orders of magnitude..

See except for the recent The Verge interview (see link in the comments) with Valve.

Griffais says the company is also directly paying more than 100 open-source developers to work on the Proton compatibility layer, the Mesa graphics driver, and Vulkan, among other tasks like Steam for Linux and Chromebooks.

This is how Linux gaming has been able to narrow the gap with Windows by investing millions of dollars a year in improvements.

If it wasn't for Valve and Red Hat, the Linux desktop and gaming would be decades behind where it is today.

I'm an Electron maintainer. We recently (finally!) switched the framework over to Wayland by default, and it's been a bigger change than a lot of people realize. This post covers how the migration took place and its consequences for apps, plus everyone's favourite uncontroversial topic, CSD. Happy to answer questions here as well.