Some, older video drivers specific to proprietary Sun video boards such most of their early once but also one of the last of it’s kinds Creator / Elite 3d do not have a mode-setting open source Linux driver. To set another video mode for those you “currently” need to do so from the OBP / OpenFirmware, such as:
setenv output-device screen:r1600×1000x66
Unfortunately usually the cards open firmware glue does not support any arbitrary mode with this so you need to check against a list of officially Sun supported modes, … :-/ However, you can at least test what you set with
Once upon a time, in a galaxy far away the first digital flat panel (DFP) displays where digitally connected not by DVI, butOpen LDI: a high-bandwidth digital-video interface standard for connecting graphics/video processors to flat panel LCD monitors. It was based on the FPD-Link specification, which was the standard for transferring graphics and video data through notebook hinges since the late 1990s. Both OpenLDI and FPD-Link use low-voltage differential signaling (LVDS) as the physical layer. The SGI 1600SW was the only monitor produced in significant quantities with an OpenLDI connection (though it had minor differences from the final published standards):
If you were wondering why your Bluetooth devices, such as keyboard and mouse, (…) do not automatically reconnect when you reboot / start your Linux desktop, … It is not enough to just have the bluetooth deamon running. You also need to power it up:
libexec/bluetooth/bluetoothd
bluetoothctl power on
You obviously had to pair and connect the device, before but you also need to trust (because obviously “pairing” is not trusting) …
With this years of Apple’s macOS 10.15 aka “Catalina”, Apple removed support for 32-bit applications, as well as deprecated and removed a log of other stuff as usually. The consequence is that lots of old, and not further maintained software and drivers do not work anymore. One very popular one are Fujitsu scanners, such as the ScanSnap ix500, 1500, and Canon P-215 or other DR series devices.
However, you do not need to obsolete and recycle or sell the scanner, nor buy new ones! ExactScan does include some 500 built-in drivers for scanners like this, including those Fujitsu ScanSnap ix500, 1500, and even many much older ones, such as other popular models like the fi-5110EOX.
ExactScan does not only allow to continue using all these scanners, it even has some more, advanced image processing options and enhancements, and the Pro version includes blazing fast OCR, that is up to 10 times faster than what most vendors use in their scan software.
Some websites suggest a shorter, more minimal file without the country=YOUR-LOCATION, however the last time I checked that will not enable the wireless network interface, maybe intentionally due to regulatory concerns.
Over four years ago I wrote about Why monolithic kernels are fail and last night I live streamed some talk about micro kernels:
And in my famous prior art patent voiding serious I wanted to formerly disclose a potentially novel system call implementation detail idea: In multi server micro kernels context switches happen more frequent than in simple, shared address space monolithic kernel (such as Linux). This is due to device drivers (and filesystem, network stacks and hopefully everything else, ..!) hopefully running in regular, isolated processes. This is obviously great for security and stability, but naturally requires way more context switches that can hurt performance. Now slim and lightweight micro kernels (such as L4) are usually quite optimized and often require less instruction cycles for inter address space context switches, however such a horde of multiple servers will execute multiple times more of those. Now my (novel?) idea to further minimize the costs of context switches is to bundle system calls in batches (or molecules? ;-) so that an application (or device driver, after all they should now be regular processes, …!) only context switch once for a couple of system calls. The exact ABI calling convention and format has to be defined by the implementor and implementation, for simplicity let’s assume some kind of “protocol buffer”, so a open, read, seek, read sequence could look like:
The same concept obviously applies to all kind of similar operations, and is somewhat similar to the existing Unix concept of writev(), and it’s iovec structure – just way more generic and flexible.
As a bonus point for more flexibility, one could either implement it so, that the syscalls are executed one-by-one until the first error, or optional –for a little more flexibility– introduce flags / tags of groups to execute until and error occurs or not. E.g. the operations might be related to two different file descriptors, so the other tagged group could still be executed, even when one of them failed. Obviously error checking for the calling application becomes a multi return value operations, instead of just a single if (!read/write/…) {} block.
