3 ms·
>With BSDs That like saying Linux and Android. Sorry, they are not comparable at all. FreeBSD uses modules, OpenBSD doesn't. FreeBSD uses X, OpenBSD uses Xenoc
by anthk 4y ago
>With BSDs
That like saying Linux and Android. Sorry, they are not comparable at all. FreeBSD uses modules, OpenBSD doesn't. FreeBSD uses X, OpenBSD uses Xenocara, a fork. FreeBSD's X.org setup can be madness, OpenBSD with XFCE it's ridiculously simple.
For instance, ACPI keys for brightness under OpenBSD work everywhere, not just under X.
>Touchpad
You must do that under Linux too, in order to use the working Synaptics module for X.org (for some laptops) instead of libinput/evdev or whatever is called today. It happened to me. Default module: jumping cursor, unusable. It worked as if it were an absolute device to the screen instead of relative movement. Synaptics: working.
- dark-star 4y ago>That like saying Linux and Android [...] I'm well aware that they are not the same, but I tried both FreeBSD and OpenBSD, and for simplicity I consolidated them in my post. Sorry if that offended you. > You must do that under Linux too The touchpad worked flawlessly out of the box for me (on Manjaro), including two-finger scrolling and tap-to-click. No idea what driver it uses though All in all, the original post encouraged me to try OpenBSD again soon(ish), who knows, maybe it works better these days...
- dark-star 4y agoOkay, I just spent about 2 hours trying to get OpenBSD 7.2 (amd64) working on my laptop (Dell Latitude E6540). Things I noticed: - The installer worked fine - It detected the WWAN and WiFi cards, although it couldn't get the WiFi working due to missing firmware (that was expected) - The installer complained that the USB image was insecure because it was missing a SHA256 signature for the files. I re-downloaded it from a different mirror but that was bit-for-bit identical to the one I had, so I think this is probably just a bug in the installer (or image) Installation went quick and I was met with a "Congratulations" message, where I opted to reboot. After that, the laptop entered a boot loop, with every reboot resulting in it rebooting again right after the BIOS logo, without even as much as a text screen/boot loader showing. I figured it might be because I installed as GPT (which was what the installer suggested) even though my BIOS is set to legacy boot. So I re-did the installation, this time choosing "whole disk (MBR)" instead of "whole disk (GPT)". The reboot loop didn't happen again, but it still couldn't boot from the disk, no text output, nothing, just the big BIOS logo and half a second of flashing the HDD LED, then silence. Trying the BIOS-integrated boot menu (F12) hung the whole laptop unless I removed the harddisk. The disk itself is fine though (I gave it a quick run-down on my desktop system) and another disk with Linux on it still boots without issue. So yeah, maybe OpenBSD probably isn't right for me if I expect as much as a basic, working system after installation shrug