On 1/21/20 10:54 PM, John Jason Jordan wrote:
First, are you sure the 390 driver is the right one for your card?
Yes. It's been working for several years.
If I
recall correctly, when you select the driver in Synaptic there is a box
below the list of packages that gives you information about the driver.
Last time I looked it said things like 'for the G-blob series of
chips.'
As for messages, look at /var/log/messages. It's a long document, but
if you open it in Mousepad or Gedit you can do a search on things like
'nvidia' and such.
Oh, and I find it interesting that you have an Intel CPU, but lshw
didn't find the video on it. Maybe your Intel CPU doesn't come with
video.
And another thought - we seem to assume that the problem must be
software. What if the card is not properly seated? What if it's really
kaput? I had the nVidia chip on my old laptop fail after six months or
so. Do you have another video card you can stick in the machine for a
test? (Hint: Free Geek has a lot of them.)
That's all I can think of for now.
Thanks. I'll have some time later to try those things.
Yesterday I let my Lenovo X200 run the update. It is also Xubuntu 18.04.
It doesn't have nVidia, and it came up fine. But I didn't try running
VirtualBox. I don't have Win7 on it, but I do have Win2K. VirtualBox
gives me the following when I try to run it:
Failed to open a session for the virtual machine Win2k.
The virtual machine 'Win2k' has terminated unexpectedly during startup
with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
It also told me to run /sbin/vboxconfig. I did. This is what I got:
rsteff@richard-ThinkPad-X200-Tablet:~$ sudo /sbin/vboxconfig
[sudo] password for rsteff:
vboxdrv.sh: Stopping VirtualBox services.
depmod: WARNING: could not open
/lib/modules/5.0.0-36-generic/modules.order: No such file or directory
depmod: WARNING: could not open
/lib/modules/5.0.0-36-generic/modules.builtin: No such file or directory
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what
went wrong.
I'll do that later, too. It went on to say:
There were problems setting up VirtualBox. To re-start the set-up
process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you
can load
them. Please see your Linux system's documentation for more information.
rsteff@richard-ThinkPad-X200-Tablet:~$
I don't recall if the X200 has UEFI.
Maybe there are some hints to be found there. I have work this morning,
so more digging later.
--
Regards,
Dick Steffens
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
