If I now run run hwinfo – gfxcard I get the output: 08: PCI 02.0: 0300 VGA compatible controller (VGA)Ĭonfig Status: cfg=new, avail=yes, need=no, active=unknown Could not connect to the bumblebee daemon - is it running? The Bumblebee daemon has not been started yet or the socket path tatus was incorrect I tested to see if Bumblebee was working by running optirun -status I have followed the instructions for setting up Bumblebee as in Sauerland’s answer and link and restarted the machine. ![]() I’m guessing you need to investigate Sauerland’s answer. Module Alias: "pci:v000010DEd00001D10sv0000103Csd000083ADbc03sc02i00"ĭriver Activation Cmd: "modprobe nouveau"ĭriver Activation Cmd: "modprobe nvidia_drm"Īgain, it seems the nvidia driver is active. Memory Range: 0xb0000000-0xb1ffffff (ro,non-prefetchable) Memory Range: 0xa0000000-0xafffffff (ro,non-prefetchable) Memory Range: 0xb3000000-0xb3ffffff (rw,non-prefetchable) Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable) Memory Range: 0xb2000000-0xb2ffffff (rw,non-prefetchable) SubVendor: pci 0x103c "Hewlett-Packard Company" Output of hwinfo -gfxcard is: 08: PCI 02.0: 0300 VGA compatible controller (VGA) this is presumably the driver for the integrated graphics which Leap 42.3 defaults to. The Info Centre: Graphical Information: OpenGL shows the driver as OpenGL version 3.0 Mesa 17.0.5 from VMware Inc. The nvidia G04 drivers are already installed (with drm-kmp-default removed) but they are not used since the nvidia graphics system seems not to be used. Like mattinthehat I have tried running nvidia-config with the same disastrous results - I could only recover by doing a snapper rollback. ![]() There appears to be no graphics configuration available under YAST. Anyway, I want to use the NVIDIA graphics (identified as nVidia GeForce MX150 in Windows). This may be the cause of the machine running hot when booted into openSUSE Leap 42.3. The installation of Leap 42.3 appears to have defaulted to the integrated graphics (identified as Intel UHD Graphics 620 when the machine is booted into Windows). Subsystem: Hewlett-Packard Company Device Ġ0:04.0 Signal processing controller : Intel Corporation Skylake Processor Thermal Subsystem (rev 08)Ġ1:00.0 3D controller : NVIDIA Corporation Device (rev a1) My output: 00:02.0 VGA compatible controller : Intel Corporation Device (rev 07) I have a similar, perhaps identical, issue on my machine. System hangs at boot, and going into a tty console makes the monitor flash like a rave so I have to try to get in from the grub. When I run the nvidia-xconfig - it says their was no config file to begin with, so It creates a new one. Their is no force composition pipeline in /etc/X11/nf. Kernel modules: nouveau, nvidia_drm, nvidiaĠ3:00.0 Network controller : Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) Subsystem: Acer Incorporated Device Ġ1:00.0 3D controller : NVIDIA Corporation Device (rev a2) ![]() Mattinthehat: Yes I am aware of Bumblebee but on Ubuntu based distros the Nvidia X server settings allowed me to just run the graphics card.Ġ0:02.0 VGA compatible controller : Intel Corporation HD Graphics 620 (rev 02) # generated from data in "/etc/sysconfig/mouse" Is created at /etc/X11/XF86Config with default settings.įor reference, here is the nf created for my system by the official 390.25 driver installer: # nvidia-xconfig: X configuration file generated by nvidia-xconfig If no X config file can be found, a new one ![]() Reads an existing X config file and adapts it to use the NVIDIA driver. etc/X11/-xconfig-original the first time it makes changes to that file. As an example, nvidia-xconfig will copy an X configuration file at /etc/X11/nf to Previously touched this is assumed to be an X configuration file that predates the involvement of the NVIDIA Xĭriver. This type of backup is made by nvidia-xconfig before it modifies an X configuration file that it has not Restore a backup of the X configuration that was made before any changes were made by nvidia-xconfig, if such a backup For example, if your X configuration is /etc/X11/nf then nvidia-xconfig will copy it to /etc/X11/ before writing the new configuration. If you enabled “Force Composition Pipeline” and it was added to /etc/X11/nf, that can cause the desktop to freeze when loading.Ī backup of the original configuration is created with “.backup” appended.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |