# FreeBSD and X woes // 19-7-16

Last week, during our moving (there'll be another post) and so
without any spare time, I did updates on my laptops, and X stopped
working. Bummer. Now of course I prefer to live in the CLI environment,
but for online banking and other stuff, I need graphical browsers and PDF
viewers, unfortunately.  So I was rather upset. Two days ago, I started
peeking around on fora (a lot of people like to call them forums) and
in search engine results, but could not find anything useful.  X simply
said it was ignoring the vesa device which was "bound by kernel". Someone
on FreeBSD forum claimed there must be some kernel module occupying the
device, which I could not believe. There was one helpful hint, saying
it was an issue of libpciaccess libraries no longer working correctly.

And so before updating my work desktop (with the same OS version), I
backed the library files up. Afterwards, it suffered from the exact same
issue, but simply coping back two libpciaccess libraries solved it! I also
copied them over to my laptops, and everything worked again as before.

I wonder how one can downgrade ports in FreeBSD without working from
sources and compiling them. It would be nice to have a "rollback" scheme,
but I'm not yet aware of an official method. I posted to the FreeBSD
forum; we'll see.

Such events are really annoying.

.:.