I have previously commented that xorg-minimal works but I have just tried it with xf86-video-intel (with /xorg.conf.d/driver-intel.conf) and got:
"EE No screens found"
I can post my Xorg.0.log if anyone is interested.
Note that I have Skylake C/GPU and I do not know if these are supported with -intel, I am fairly new to BSD world and do not know if my issue is related.
PS. drm-kmod works for me just fine, I just wonder if drm-kmod adds additional layer because I see some freezes on my system
I suggest you state your case here: https://www.x.org/wiki/DeveloperStart/The best would be to have a BSD-X11 non dependent of Linux.
That's a very good idea. I appreciate your post. It is really clean and nice, often / always helpful.I suggest you state your case here: https://www.x.org/wiki/DeveloperStart/
I helped users to make work their machines.[USER=1677]@SirDice[/USER], can you least temporary ban Spartrekus until PR 239065 is resolved?
No, you're being obtuse and intentionally disruptive.I helped users to make work their machines.
Indeed. You now have plenty of time during the next 7 days.Sure you can.
this line also shows up in my /var/log/Xorg.0.log and my 'CLI-only' box also has version 0.14 of libpciaccess
No, you're being obtuse and intentionally disruptive.
Indeed. You now have plenty of time during the next 7 days.
this line also shows up in my /var/log/Xorg.0.log and my 'CLI-only' box also has version 0.14 of libpciaccess
cd /usr/ports/devel/libpciaccess svn update -r438045 make clean make reinstall
remedies suggested by other participants of this thread have failed to fix the "no screens found" error on my (and others') PC.
Your situation I consider an acceptable loss, of course.
You arrived here with Xorg.0.log prominently displaying the message from nvidia-driver v. 340: "The NVIDIA GeForce4 440 Go GPU installed in this system is supported through the NVIDIA 96.43.xx Legacy drivers." Then you demanded to make it work regardless.....
Can you build libpciaccess 0.13.5 from source?
Or just grab it (only this package!) from release_0 repo, doesn't really matter.
# pkg downgrade -1 <package>
, where `-1' would be one release-version back)I'll just try to dissolve the tension a bit here (and I'm not a mod). [USER=52920]Spartrekus[/USER] isn't banned, but he has been put on a timeout. Consider the postings he did in the other thread as the proverbial drop in the bucket.Of course, at this point, it's all academic since the problem's been fixed. Again, my apologies if I've offended or inconvenienced you. It certainly was NOT intentional. Peace.
rm -rf /var/cache/pkg/*
pkg upgrade -f
and all packages will be updated. Don't worry, you can always go back to the solution you already had.cd /usr/ports/devel/libpciaccess svn update -r438045 make clean make reinstall
portsnap
) and I suspect that's where it went wrong. portsnap
, Subversion/SVN and Git.This will only work if the ports tree you have is actually checked out using subversion.
mkdir ~/libpciaccess-workaround cd ~/libpciaccess-workaround portdowngrade devel/libpciaccess 438045 cd libpciaccess make reinstall
You mentioned it "didn't work". What exactly in these commands didn't work?
So if you let us/me know how you installed the ports tree we can work from there. The general possibilities are the "normal" way usingportsnap
, Subversion/SVN and Git.
Well, these commands are updating FreeBSD (the base OS as it's known).When completed, the first thing I do is run "freebsd-update fetch" and "freebsd-update extract". It's here (within the ports) where I reckon the problem's occurring, but that's just a hunch.
freebsd-update install
portsnap fetch && portsnap update
. That is of course normally only relevant if you are not using packages, but since the problem you're hitting is related to packages you'll have toWell, these commands are updating FreeBSD (the base OS as it's known).
EDIT: note that your second command is wrong. It should befreebsd-update install
This will not give you the latest ports tree in any way or shape.
For that, you need to runportsnap fetch && portsnap update
. That is of course normally only relevant if you are not using packages, but since the problem you're hitting is related to packages you'll have to
compile devel/libpciaccess from ports until the problem has been fixed. See [USER=54069]shkhln[/USER]'s post right above your post for relevant commands.
Code:mkdir ~/libpciaccess-workaround cd ~/libpciaccess-workaround portdowngrade devel/libpciaccess 438045 cd libpciaccess make reinstall
portdowngrade
noted a clear and explicit "stop" because of known vulnerabilities in libpciaccess 0.13.5. So I stopped, but found it remarkable that this warning was not given on a 32-bit system.