X stopped working after upgrading to 14.3.

I checked dmesg -a and discovered a couple of things which I am having some difficulty "translating". I'll list them in order.

atrtc0 can't map interrupt
hdac1 CODEC at address 2 not responding
KLD nvidia-modeset.ko depends on kernel not available or version mismatch
kldload: can't load nvidia_modeset: module already loaded or in kernel
/etc/rc WARNING Unable to load kernel module nvidia-modeset
/etc/rc WARNING unable to load kernel module usbhid
Invalid TXQ id

So, it looks to me as though nvidia-modeset is not being loaded at all.

Ken Gordon
 
1. Show us what "uname -a" says. Make sure you have 14.3. or else your upgrade to 14.3 failed.
2. Show us the first "url:" line in /etc/pkg/FreeBSD.conf -- it should be url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
3. pkg install -f nvidia-kmod -- to make sure you have the correct bits.
4. Reboot. After that see from dmesg if nvidia-modeset loaded. If not, show us what the nvidia related lines are. 1. & 2. above ensure you have matching kernel and .ko files.
 
KenGordon said:
So, it looks to me as though nvidia-modeset is not being loaded at all.
Click to expand...
No. It's loaded as 4th line of your dmesg shows. Just not working as of mis-match with kernel.

So, request 1 by bakul in post #27 is important here.
If you're building ports locally, running (or to be run after next reboot) kernel and kernel sources (under /usr/src/sys/) are needed to be in sync. Otherwise, the error you encountered could happen (not always, though).
 
bakul said:
1. Show us what "uname -a" says. Make sure you have 14.3. or else your upgrade to 14.3 failed.
Click to expand...

uname -ashows 14.3-RELEASE-p5. I remember this from doing it a few days ago. I'll re-run that the next time I boot into FreeBSD (I am in Win10 just now) and will list the exact output from the command.

bakul said:
2. Show us the first "url:" line in /etc/pkg/FreeBSD.conf -- it should be url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
Click to expand...

That URL line is https://pkg.FreeBSDS.org/$(AB1)/quarterly. I had to remove the pkg+ from those lines in order for the upgrades to work. I believe, now, that the reason was that the {SRV} line was missing in that set of commands. I'll revisit those commands, reinsert the pkg+ part. and add the line containing {SRV} then try to correct matters.

bakul said:
3. pkg install -f nvidia-kmod -- to make sure you have the correct bits.
Click to expand...

OK.

bakul said:
4. Reboot. After that see from dmesg if nvidia-modeset loaded. If not, show us what the nvidia related lines are. 1. & 2. above ensure you have matching kernel and .ko files.
Click to expand...

Will do. And thanks again.

Ken Gordon
 
KenGordon said:
That URL line is https://pkg.FreeBSDS.org/$(AB1)/quarterly.
Click to expand...
There are mutiple typo's in your line (no use of curly braces and no capital I, the I of Isaac ), check your actual reference:
Rich (BB code): 
    you have:     https://pkg.FreeBSDS.org/$(AB1)/quarterly
it should be: pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
The addition of "pkg+" should work but we can deal with that later.

Just to be sure about your settings, please post (cut & paste) the output of
pkg -vv | sed -nE -e '/^OSVERSION|^ABI/ p' -e '/^Repositories:/,$ p'
 
Yeah, there's lots of times when a typo is all that stands between me and a successful setup of just about anything. That really taught me to be incredibly anal about them, and to never be in a rush typing stuff out. That's actually easier than trying to learn a sed/awk command to do the same thing and trying to debug THAT later 😂
 
I happened to have 14.3-RELEASE bhyve VM so I fired it up, freebsd-updated it to -p5, rebooted, installed nvidia-kmod and kldloaded nvidia-modeset. kldstat & dmesg showed nvidia-modeset.ko and nvidia.ko loaded fine. I am not passing the GPU to this VM but this shouldn't matter for now. So not sure what is going on with Ken's machine....
 
Erichans said:
There are mutiple typo's in your line (no use of curly braces and no capital I, the I of Isaac ), check your actual reference:
Rich (BB code): 
    you have:     https://pkg.FreeBSDS.org/$(AB1)/quarterly
it should be: pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
Click to expand...

Yes, there are multiple typos in that post because I am not copying from my FreeBSD system, but am writing it all down on paper, then typing it in here. I am 83 years old and my eyesight is no longer very good.

So, here are two photos of what I meant to show: the first one is they way it was at first and the second photo is after I fixed it. FYI, adding the
Code: 
pkg+
required me to also add the line
Code: 
mirror_type: "srv"
. Without that line, including
Code: 
pkg+
caused everything to fail. Here are the photos:
FreeBSD_conf.jpg


and after editing it:
FreeBSD_conf2.jpg


Erichans said:
The addition of "pkg+" should work but we can deal with that later.
Click to expand...

Well, only if the line mirror_type: "srv" is included.

Erichans said:
Just to be sure about your settings, please post (cut & paste) the output of
pkg -vv | sed -nE -e '/^OSVERSION|^ABI/ p' -e '/^Repositories:/,$ p'
Click to expand...

OK. Will do.

Ken Gordon
 
The following are photos of the results of certain commands requested by some who are trying to help me come to a conclusion on these issues. The first one shows the results of inputting uname -a as root:

uname-a.jpg


Next, shows the result of some of the latest dmesg -a showing that at least one of the nivida files is 1)not loaded, and 2) that there is a version mismatch somewhere.
Dmesg-a_Part.jpg


The last one shows the result of inputting startx as a normal user. This worked fine under 14.2-RELEASE-p3 but no longer works under 14.3-RELEASE-p5.
StartxResult.jpg


At this point, I am wondering if using freebsd-update rollback will at least put my system back to 14.2, but I doubt that will work, and at this point, I am less than enthusiastic about attempting it..

Ken Gordon
 
KenGordon said:
At this point, I am wondering if using freebsd-update rollback will at least put my system back to 14.2, but I doubt that will work, and at this point, I am less than enthusiastic about attempting it..
Click to expand...
I'm also less enthousiastic about that, most importantly because packages for 14.2-RELEASE are no longer available!

KenGordon said:
Yes, there are multiple typos in that post because I am not copying from my FreeBSD system, but am writing it all down on paper, then typing it in here. I am 83 years old and my eyesight is no longer very good.
Click to expand...
No worries. I'm guessing and hoping that you are not responding by means of typing things on a mobile phone of sorts but on a system on hand running perhaps MS Windows.

I mention this as an option to perhaps consider trying later (we can deal with photo's under these exceptional circumstances); for example from Windows you can set up a terminal connection by means of PuTTY and then given a working network connections of course, you can easily cut and paste any non-graphical stuff.
 
A couple more things to try to see what is going on. Report what kldxref -d /boot/modules/nvidia-modeset.ko returns. I get
# kldxref -d /boot/modules/nvidia-modeset.ko
/boot/modules/nvidia-modeset.ko
module nvidia_modeset
depends on kernel.1403000 (1403000,1499999)
interface nvidia_modeset.1
depends on nvidia.1 (1,1)
depends on linux.1 (1,1)
depends on linux_common.1 (1,1)
That kernel.1403000 line indicates the kernel version(s) for which this .ko will supposedly work.

Second report what md5 /boot/modules/nvidia.ko /boot/modules/nvidia-modeset.ko returns. I get
# md5 /boot/modules/nvidia.ko /boot/modules/nvidia-modeset.ko /boot/kernel/kernel
MD5 (/boot/modules/nvidia.ko) = 6189c33384d10ad6ff34e73312eda90d
MD5 (/boot/modules/nvidia-modeset.ko) = cd99eb9a6c7bc03be69826caff9f2d31
MD5 (/boot/kernel/kernel) = fc523e4840a1bc75f11c4c46b3e5b2b0

Third see if /boot/kernel/linker.hints and /boot/modules/linker.hints exist. They are created by kldxref.
 
Thank you all for the suggestions. I will follow up on those asap. Dinner time here now, and we have guests.

I must admit to getting darned tired of dealing with this issue. I MAY decide to wait until Ver. 15-RELEASE is available, and then do a complete start-over.

As I have mentioned here several times, my main reason for moving to FreeBSD in the first place was to get completely rid of Billy Gates' garbage. And I had come very close to achieving what I wanted before running into this problem.

Rats!

Ken Gordon
 
I think it helps to have a backup plan for when your graphics go out. This is one of the FreeBSD quirks you must navigate.
Generally I don't touch my packages when we are between major versions switch. It can be a minefield.
SCFB is not that bad.
True that the resolution is limited to GOP sizes and it is not accelerated but for a short stint in a position like this it should be considered.
There is no way I would dump my desktop for a graphics problem.

example 4
docs.freebsd.org

Chapter 5. The X Window System

This chapter describes how to install and configure the X Window System providing a graphical environment
docs.freebsd.org docs.freebsd.org
 
Also note this from above manual:
To configure multiple graphics processors, the BusID can be added.A list of graphics processor bus IDs can be displayed by executing:
Click to expand...

If you have dual graphics like Optimus laptop you need to add Intel CPU graphics BUSID to scfb configuration file.
 
You must log in or register to reply here.
Back
Top