On Sat, 2019-02-23 at 13:23 +1100, Stephen Morris wrote:
> > AFAIK neither of these '3D acceleration' modes are useful for games. To
> > use the Nvidia drivers in the VM guest the only option is to pass the
> > GPU card directly through to the VM. This means masking it (i.e.
> > blacklisting) in Li
On 22/2/19 11:00 pm, Patrick O'Callaghan wrote:
On Fri, 2019-02-22 at 20:21 +1100, Stephen Morris wrote:
Note that if you actually want to use the Nvidia card to its full
capability within a VM, you need to use GPU passthrough. AFAIK this
currently cannot be done in VMware or Virtual Box, only o
On Fri, 2019-02-22 at 20:21 +1100, Stephen Morris wrote:
> > Note that if you actually want to use the Nvidia card to its full
> > capability within a VM, you need to use GPU passthrough. AFAIK this
> > currently cannot be done in VMware or Virtual Box, only on KVM/QEMU.
> > It's something of a has
On 21/2/19 11:22 pm, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 22:32 +1100, Stephen Morris wrote:
On 21/2/19 9:48 pm, Ed Greshko wrote:
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/2
On 21/2/19 11:28 pm, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 23:00 +1100, Stephen Morris wrote:
Putting the following section in xorg.conf caused Gnome under Xorg to
start with the resolution of the Maximized vmware player, which was
1600x844, as desired. KDE did not start at the resolu
On Thu, 2019-02-21 at 23:00 +1100, Stephen Morris wrote:
> Putting the following section in xorg.conf caused Gnome under Xorg to
> start with the resolution of the Maximized vmware player, which was
> 1600x844, as desired. KDE did not start at the resolution of 1600x844,
> instead starting at 64
On Thu, 2019-02-21 at 22:32 +1100, Stephen Morris wrote:
> On 21/2/19 9:48 pm, Ed Greshko wrote:
> > On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
> > > On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
> > > > On 21/2/19 6:47 am, Samuel Sieb wrote:
> > > > > On 2/20/19 1:02 AM, Stephen Mor
On 21/2/19 10:32 pm, Stephen Morris wrote:
On 21/2/19 9:48 pm, Ed Greshko wrote:
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the followi
On 21/2/19 9:48 pm, Ed Greshko wrote:
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compa
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
> On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
>> On 21/2/19 6:47 am, Samuel Sieb wrote:
>>> On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compatible controller: VMw
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
> On 21/2/19 6:47 am, Samuel Sieb wrote:
> > On 2/20/19 1:02 AM, Stephen Morris wrote:
> > > lspci provides the following output for the device:
> > >
> > > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter
> >
> > As Patrick pointe
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compatible controller: VMware SVGA II Adapter
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actua
On 2/20/19 12:01 PM, Joe Zeff wrote:
On 02/20/2019 12:47 PM, Samuel Sieb wrote:
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actually handling it, by running "lspci -v".
There will be a line with "Kernel driver in use:".
Or, just run lspci |
On 02/20/2019 12:47 PM, Samuel Sieb wrote:
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actually handling it, by running "lspci -v".
There will be a line with "Kernel driver in use:".
Or, just run lspci | grep VGA and find out right there.
___
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compatible controller: VMware SVGA II Adapter
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actually handling it, by running "lspci -v".
On Wed, 2019-02-20 at 20:02 +1100, Stephen Morris wrote:
> On 20/2/19 4:55 pm, Samuel Sieb wrote:
> > On 2/19/19 1:37 AM, Stephen Morris wrote:
> > > I found the Xorg log and found the issue, Xorg couldn't find any
> > > screens to use with the Nvidia driver. Below is the data on the
> > > chipse
On 20/2/19 4:55 pm, Samuel Sieb wrote:
On 2/19/19 1:37 AM, Stephen Morris wrote:
I found the Xorg log and found the issue, Xorg couldn't find any
screens to use with the Nvidia driver. Below is the data on the
chipset that Xorg thinks is available.
(--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 re
On 2/19/19 1:37 AM, Stephen Morris wrote:
I found the Xorg log and found the issue, Xorg couldn't find any screens
to use with the Nvidia driver. Below is the data on the chipset that
Xorg thinks is available.
(--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @
0xe800/134217728, 0xfe000
On 19/2/19 7:44 pm, Stephen Morris wrote:
On 19/2/19 7:17 pm, Stephen Morris wrote:
On 19/2/19 4:25 am, Rex Dieter wrote:
Stephen Morris wrote:
Given that it seems that F29 is standardizing
on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
group also install this package to
On 19/2/19 7:17 pm, Stephen Morris wrote:
On 19/2/19 4:25 am, Rex Dieter wrote:
Stephen Morris wrote:
Given that it seems that F29 is standardizing
on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
group also install this package to provide the needed Wayland
support so
KDE
On 19/2/19 4:25 am, Rex Dieter wrote:
Stephen Morris wrote:
Given that it seems that F29 is standardizing
on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
group also install this package to provide the needed Wayland support so
KDE can be started under Wayland, rather than re
On 18/2/19 11:49 pm, Patrick O'Callaghan wrote:
On Mon, 2019-02-18 at 17:51 +0700, Outback Dingo wrote:
On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
wrote:
On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
Hi,
In order to install the KDE Desktop I used DNF to install the
Stephen Morris wrote:
> Given that it seems that F29 is standardizing
> on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
> group also install this package to provide the needed Wayland support so
> KDE can be started under Wayland, rather than require the user to
> install it ma
On Mon, 2019-02-18 at 17:51 +0700, Outback Dingo wrote:
> On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
> wrote:
> > On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
> > > Hi,
> > >
> > > In order to install the KDE Desktop I used DNF to install the
> > > KDE-desktop-environmen
On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
wrote:
>
> On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
> > Hi,
> >
> > In order to install the KDE Desktop I used DNF to install the
> > KDE-desktop-environment group, which place a plasma entry in the desktop
> > manager deskto
On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
> Hi,
>
> In order to install the KDE Desktop I used DNF to install the
> KDE-desktop-environment group, which place a plasma entry in the desktop
> manager desktop list, but selecting this entry did not boot into KDE, it
> just cont
Hi,
In order to install the KDE Desktop I used DNF to install the
KDE-desktop-environment group, which place a plasma entry in the desktop
manager desktop list, but selecting this entry did not boot into KDE, it
just continued to display the Desktop Manager. It wasn't until I
manually ins
27 matches
Mail list logo
