Hey #bsd folks, do you suggest I use #freebsd or #openbsd for desktop usage?
#usebsd

It's been a roller-coaster-like experience for me I guess: though I tried many possible ways in vain to get #OpenBSD S3 suspend/resume to work properly, today I found out S5 hibernate actually worked flawlessly. Even my WiFi dodge came back connected! Next thing, let's hope amd64 boot support get fixed soon . #UseBSD #BSD #Unix #FOSS

How does it make sense if I boot up #OpenBSD 7.6, put it to S3 suspend, resume and everything but WiFi connection is back. But if I suspend again and try to resume, it will fail. What's different between a first time and second time suspend? #UseBSD #Unix #FOSS

Big surprise from today's little test: while #FreeBSD and #NetBSD both failed to resume from S3 suspend. It magically just worked on #OpenBSD! WiFI is down after resume but simply restart network service fixed it. 1/2 #UseBSD #Unix #FOSS

I should also add that for my wireless card Atheros 5424/2424, while #FreeBSD and #OpenBSD both had no problem detecting it and configuring with ifconfig ( sometimes even connected to my WiFi!). But only under #NetBSD it is working out of box, and continuously to just work without any disconnection or error messages popping out in dmesg. #BSD #UseBSD #Unix #FOSS

More tests today: Following #OpenBSD and #FreeBSD, I tried #NetBSD on my laptop today. I never expected but it was the best ever. #XDM started out of box with a nice #CTWM sesssion after login, WiFi connects after a few lines ifconfig commands. Suspending to S3 worked but resume resulted in no keyboard or touchpad response. Will look into this. #BSD #UseBSD #Unix #FOSS

Does amd64 support (64 bit) mean different things for #OpenBSD and #FreeBSD ? Because on my laptop with Intel Pentium T2390, which supports 64 bit systems, booting latest #OpenBSD 7.6 installation media resulted in a crash shortly after loading kernel, while #FreeBSD REL 13.1 happily booted and allowed me to install to hard disk or play around in live mode.
#Unix #BSD #UseBSD #FOSS

Also strange thing I have to figure out: my laptop running #Debian #Linux and the laptop in question running #FreeBSD are connecting to my home WiFi. I can ssh from #FreeBSD to #Debian easily, but trying ssh from #Debian to #FreeBSD is reporting `No route to host`. #BSD #UseBSD #FOSS #Unix

#FreeBSD : In my case I think it is getting very close though. When trying to resume from suspend. The keyboard, power and HDD indicator led all came back on, fan weirdly stop and then on for a few seconds and then off again repeatedly. But input is not working, screen stays forever black and off. #BSD #UseBSD #FOSS #Unix

More tests on #FreeBSD suspend/resume today, still no luck. Tried acpi_wmi, acpi_hp and acpi_ibm sequentially. When debug.acpi.suspend_bounce=1 and beep=1 was set, zzz worked and got a beep every time. But suspend_bounce=0 resulted in straight black scree and no response when trying to resume, had to shutdown hard by long pressing power button. #BSD #UseBSD #FOSS #Unix

2/2: I mean, I got this other laptop also more than ten year old, which only has a #Nvidia video card. But actually suspend/resume worked flawlessly almost out of box when I ran #FreeBSD 13. #BSD #UseBSD #FOSS #Unix

1/2: And I never thought I would have to deal with suspend/resume issue with an over-10-year-old laptop which does not even have discrete video card in #FreeBSD . I mean, if it's #Nvidia I totally understand, but not with a decade year old #Intel video card. #BSD #UseBSD #FOSS

What does `sysctl debug.acpi.suspend_bounce=1` in #FreeBSD do? I saw in a forum thread saying it is just simulating S3 suspend while system stays awake. But my laptop screen went off and power led does not blink at all, meaning screen IS suspending and nothing else. #BSD #UseBSD #FOSS #Unix

Happy 28th birthday to the #NetBSD project.