KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29

[Stephen Morris]

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 installed, I think, the plasma-workspace-wayland that 'plasma 
for wayland' was added to the desktop list in the display that did 
enable KDE to be started. 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 manually?

regards,

Steve

[Patrick O'Callaghan]

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 continued to display the Desktop Manager. It wasn't until I 
>  manually installed, I think, the plasma-workspace-wayland that 'plasma 
>  for wayland' was added to the desktop list in the display that did 
>  enable KDE to be started. 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 manually? 
AFAIK KDE under Wayland is still quite experimental. In any case the
best place to ask would be the Fedora KDE list:

https://lists.fedoraproject.org/archives/list/[e-mail]/

poc

[Outback Dingo]

On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
<pocallaghan(a)gmail.com&gt; 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 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 installed, I think, the plasma-workspace-wayland that 'plasma
>  > for wayland' was added to the desktop list in the display that did
>  > enable KDE to be started. 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 manually?
>
>  AFAIK KDE under Wayland is still quite experimental. In any case the
>  best place to ask would be the Fedora KDE list:
>
>  https://lists.fedoraproject.org/archives/list/[e-mail]/
>  
No idea why people try this route when the F29 KDE Plasma spin works
perfectly fine...

> poc
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Patrick O'Callaghan]

On Mon, 2019-02-18 at 17:51 +0700, Outback Dingo wrote:
>  On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
>  <pocallaghan(a)gmail.com&gt; 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 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 installed, I think, the plasma-workspace-wayland that 'plasma
>  > > for wayland' was added to the desktop list in the display that did
>  > > enable KDE to be started. 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 manually?
>  > 
>  > AFAIK KDE under Wayland is still quite experimental. In any case the
>  > best place to ask would be the Fedora KDE list:
>  > 
>  > https://lists.fedoraproject.org/archives/list/[e-mail]/
>  > 
>  
>  No idea why people try this route when the F29 KDE Plasma spin works
>  perfectly fine... 
Because he already has Fedora installed and simply wants to add a
different DE?

poc

[Rex Dieter]

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 manually? 
Only gnome has standardized on wayland, KDE has not.  KDE's wayland session 
support is at best still experimental.

That said, the Xorg-based kde session not starting is not good. Finding out 
why that fails would be a more useful exercise.

-- Rex

[Stephen Morris]

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
> > <pocallaghan(a)gmail.com&gt; 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 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 installed, I think, the plasma-workspace-wayland that 'plasma
> >>> for wayland' was added to the desktop list in the display that did
> >>> enable KDE to be started. 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 manually?
> >> AFAIK KDE under Wayland is still quite experimental. In any case the
> >> best place to ask would be the Fedora KDE list:
> >>
> >> https://lists.fedoraproject.org/archives/list/[e-mail]/
> >>
> > No idea why people try this route when the F29 KDE Plasma spin works
> > perfectly fine...
>  Because he already has Fedora installed and simply wants to add a
>  different DE? 
The live installer installs Gnome by default, whose interface I haven't 
liked for a long time, and I much prefer using KDE, but the KDE entry 
placed on the DM does not start KDE, but the entry placed there after 
installing the wayland support for kde package does launch KDE. I'm 
still trying to find the logs created by the KDE start up to determine 
why the Plasma entry on the DM, which I assume is to start KDE under 
Xorg, doesn't actually launch KDE.


regards,

Steve

>
> poc
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Stephen Morris]

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 require the user to
> > install it manually?
>  Only gnome has standardized on wayland, KDE has not.  KDE's wayland session
>  support is at best still experimental.
>
>  That said, the Xorg-based kde session not starting is not good. Finding out
>  why that fails would be a more useful exercise. 
I'm trying to find that at the moment, but I'm not sure where the logs 
to investigate why it fails are located.


regards,

Steve


>
> -- Rex
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Stephen Morris]

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 can be started under Wayland, rather than require the user to
> >> install it manually?
> > Only gnome has standardized on wayland, KDE has not.  KDE's wayland 
> > session
> > support is at best still experimental.
> >
> > That said, the Xorg-based kde session not starting is not good. 
> > Finding out
> > why that fails would be a more useful exercise.
>
>  I'm trying to find that at the moment, but I'm not sure where the logs 
>  to investigate why it fails are located. 
I tried the Gnome on Xorg entry in the DM and that doesn't start Gnome 
either. I'll need to try and find the Xorg log to see if that indicates 
any issues.


regards,

Steve


>
>
>
> regards,
>
> Steve
>
>
>>
>> -- Rex
>> _______________________________________________
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/[e-mail]
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Stephen Morris]

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 provide the needed Wayland 
> >>> support so
> >>> KDE can be started under Wayland, rather than require the user to
> >>> install it manually?
> >> Only gnome has standardized on wayland, KDE has not.  KDE's wayland 
> >> session
> >> support is at best still experimental.
> >>
> >> That said, the Xorg-based kde session not starting is not good. 
> >> Finding out
> >> why that fails would be a more useful exercise.
> >
> > I'm trying to find that at the moment, but I'm not sure where the 
> > logs to investigate why it fails are located.
>
>  I tried the Gnome on Xorg entry in the DM and that doesn't start Gnome 
>  either. I'll need to try and find the Xorg log to see if that 
>  indicates any issues. 
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 @ 
0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 
0x????????/65536


Given that I am running in a Vmware VM, which has 3D Acceleration 
enabled, and is supposed to be able to work with 3D Accelerated video 
drivers, how do I configure Xorg to work with the above chipset that 
Xorg thinks is present?


regards,

Steve


>
>
> regards,
>
> Steve
>
>
>>
>>
>>
>> regards,
>>
>> Steve
>>
>>
>>>
>>> -- Rex
>>> _______________________________________________
>>> users mailing list -- users(a)lists.fedoraproject.org
>>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives: 
>>> https://lists.fedoraproject.org/archives/list/[e-mail]
>> _______________________________________________
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/[e-mail]
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Samuel Sieb]

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 @ 
>  0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 
>  0x????????/65536 
What does "lspci" say the video device is?

[Stephen Morris]

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 rev 0, Mem @ 
> > 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 
> > 0x????????/65536
>
>  What does "lspci" say the video device is? 
lspci provides the following output for the device:


00:0f.0 VGA compatible controller: VMware SVGA II Adapter


I've checked whether hardware acceleration is active by running 
glxgears, which runs quite happily, so I'm assuming that hardware 
acceleration, as set by the vm configuration, is actually active, hence 
the nvidia driver is functioning, so I thought Xorg would be able to 
work with the nvidia driver quite happily.


regards,

Steve

> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Patrick O'Callaghan]

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 
>  > > chipset that Xorg thinks is available.
>  > > 
>  > > (--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 
>  > > 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 
>  > > 0x????????/65536
>  > 
>  > What does "lspci" say the video device is?
>  
>  lspci provides the following output for the device:
>  
>  
>  00:0f.0 VGA compatible controller: VMware SVGA II Adapter
>  
>  
>  I've checked whether hardware acceleration is active by running 
>  glxgears, which runs quite happily, so I'm assuming that hardware 
>  acceleration, as set by the vm configuration, is actually active, hence 
>  the nvidia driver is functioning, so I thought Xorg would be able to 
>  work with the nvidia driver quite happily. 
It's not an Nvidia driver in the VM. It's a "VMware SVGA II" driver.

poc

[Samuel Sieb]

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". 
There will be a line with "Kernel driver in use:".

>  I've checked whether hardware acceleration is active by running 
>  glxgears, which runs quite happily, so I'm assuming that hardware 
>  acceleration, as set by the vm configuration, is actually active, hence 
>  the nvidia driver is functioning, so I thought Xorg would be able to 
>  work with the nvidia driver quite happily. 
That doesn't tell you that there is hardware acceleration.  There is a 
software 3D renderer available.  You can try running "glxinfo" to find 
out what is being used.  I'm not sure what that will show under Wayland.

[Joe Zeff]

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.

[Samuel Sieb]

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 | grep VGA and find out right there. 
What are you trying to say?  You cut out the device line that was right 
above the part you quoted.  I want to know what kernel driver is being 
used for the graphics and your instructions will not do that.

[Stephen Morris]

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 actually handling it, by running "lspci -v". 
>  There will be a line with "Kernel driver in use:".
>  
"lspci -v" gives me the following output:


00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 
[VGA controller])
         Subsystem: VMware SVGA II Adapter
         Flags: bus master, medium devsel, latency 64, IRQ 16
         I/O ports at 1070 [size=16]
         Memory at e8000000 (32-bit, prefetchable) [size=128M]
         Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
         [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
         Capabilities: <access denied>
         Kernel driver in use: vmwgfx
         Kernel modules: vmwgfx

This output is under Wayland. I have previously installed the nvidia 
proprietary driver from Negativo17 via dkms, and from what I can see 
from the Xorg log, Xorg is loading that driver and the corresponding glx 
module just before the message that Xorg can't find any display devices 
to use.

I also checked the xorg.conf file and it specifies to use the nvidia 
driver, should I change it to the above driver or is the above driver 
unique to Wayland?


regards,

Steve


>> I've checked whether hardware acceleration is active by running 
>> glxgears, which runs quite happily, so I'm assuming that hardware 
>> acceleration, as set by the vm configuration, is actually active, 
>> hence the nvidia driver is functioning, so I thought Xorg would be 
>> able to work with the nvidia driver quite happily.
>
> That doesn't tell you that there is hardware acceleration.  There is a 
> software 3D renderer available.  You can try running "glxinfo" to find 
> out what is being used.  I'm not sure what that will show under Wayland.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Patrick O'Callaghan]

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 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:".
>  > 
>  "lspci -v" gives me the following output:
>  
>  
>  00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 
>  [VGA controller])
>           Subsystem: VMware SVGA II Adapter
>           Flags: bus master, medium devsel, latency 64, IRQ 16
>           I/O ports at 1070 [size=16]
>           Memory at e8000000 (32-bit, prefetchable) [size=128M]
>           Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
>           [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
>           Capabilities: <access denied>
>           Kernel driver in use: vmwgfx
>           Kernel modules: vmwgfx
>  
>  This output is under Wayland. I have previously installed the nvidia 
>  proprietary driver from Negativo17 via dkms, and from what I can see 
>  from the Xorg log, Xorg is loading that driver and the corresponding glx 
>  module just before the message that Xorg can't find any display devices 
>  to use.
>  
>  I also checked the xorg.conf file and it specifies to use the nvidia 
>  driver, should I change it to the above driver or is the above driver 
>  unique to Wayland? 
The driver has nothing to do with Wayland as such. Clearly an Nvidia
driver isn't going to work with a non-Nvidia GPU, which is what your VM
has. If you're loading the Nvidia driver anyway, this may be the source
of the problem. Remove the Nvidia stuff and try again.

poc

[Ed Greshko]

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: 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". 
> >> There will be a line with "Kernel driver in use:".
> >>
> > "lspci -v" gives me the following output:
> >
> >
> > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 
> > [VGA controller])
> >          Subsystem: VMware SVGA II Adapter
> >          Flags: bus master, medium devsel, latency 64, IRQ 16
> >          I/O ports at 1070 [size=16]
> >          Memory at e8000000 (32-bit, prefetchable) [size=128M]
> >          Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
> >          [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
> >          Capabilities: <access denied>
> >          Kernel driver in use: vmwgfx
> >          Kernel modules: vmwgfx
> >
> > This output is under Wayland. I have previously installed the nvidia 
> > proprietary driver from Negativo17 via dkms, and from what I can see 
> > from the Xorg log, Xorg is loading that driver and the corresponding glx 
> > module just before the message that Xorg can't find any display devices 
> > to use.
> >
> > I also checked the xorg.conf file and it specifies to use the nvidia 
> > driver, should I change it to the above driver or is the above driver 
> > unique to Wayland?
>  The driver has nothing to do with Wayland as such. Clearly an Nvidia
>  driver isn't going to work with a non-Nvidia GPU, which is what your VM
>  has. If you're loading the Nvidia driver anyway, this may be the source
>  of the problem. Remove the Nvidia stuff and try again.
>  
Kernel driver in use: vmwgfx

vmwgfx is VMWare guest GL driver

If it were nVidia it would read

Kernel driver in use: nvidia

-- 
Right: I dislike the default color scheme Wrong: What idiot picked the default color
scheme

[Stephen Morris]

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 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".
> >>> There will be a line with "Kernel driver in use:".
> >>>
> >> "lspci -v" gives me the following output:
> >>
> >>
> >> 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00
> >> [VGA controller])
> >>           Subsystem: VMware SVGA II Adapter
> >>           Flags: bus master, medium devsel, latency 64, IRQ 16
> >>           I/O ports at 1070 [size=16]
> >>           Memory at e8000000 (32-bit, prefetchable) [size=128M]
> >>           Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
> >>           [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
> >>           Capabilities: <access denied>
> >>           Kernel driver in use: vmwgfx
> >>           Kernel modules: vmwgfx
> >>
> >> This output is under Wayland. I have previously installed the nvidia
> >> proprietary driver from Negativo17 via dkms, and from what I can see
> >> from the Xorg log, Xorg is loading that driver and the corresponding glx
> >> module just before the message that Xorg can't find any display devices
> >> to use.
> >>
> >> I also checked the xorg.conf file and it specifies to use the nvidia
> >> driver, should I change it to the above driver or is the above driver
> >> unique to Wayland?
> > The driver has nothing to do with Wayland as such. Clearly an Nvidia
> > driver isn't going to work with a non-Nvidia GPU, which is what your VM
> > has. If you're loading the Nvidia driver anyway, this may be the source
> > of the problem. Remove the Nvidia stuff and try again.
> >
>  Kernel driver in use: vmwgfx
>
>  vmwgfx is VMWare guest GL driver
>
>  If it were nVidia it would read
>
>  Kernel driver in use: nvidia 
I have tried removing the nvidia entries from the device group in 
xorg.conf, and, also specifying driver "vmware" instead of "nvidia",
and 
in both cases Gnome and KDE can be started with Xorg. In both cases 
though they start with the wrong screen resolution relative to the 
resolution that the vmware player is using. Gnome under Wayland is 
capable of re-setting its resolution to match that of the vmware player 
when maximizing the player, but KDE is not capable of doing so under 
Wayland. I might have to play around with the resolution configuration 
parameters to try to get Xorg to set its resolution to match vmware's.


regards,

Steve

[Stephen Morris]

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 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".
> >>>> There will be a line with "Kernel driver in use:".
> >>>>
> >>> "lspci -v" gives me the following output:
> >>>
> >>>
> >>> 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00
> >>> [VGA controller])
> >>>           Subsystem: VMware SVGA II Adapter
> >>>           Flags: bus master, medium devsel, latency 64, IRQ 16
> >>>           I/O ports at 1070 [size=16]
> >>>           Memory at e8000000 (32-bit, prefetchable) [size=128M]
> >>>           Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
> >>>           [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
> >>>           Capabilities: <access denied>
> >>>           Kernel driver in use: vmwgfx
> >>>           Kernel modules: vmwgfx
> >>>
> >>> This output is under Wayland. I have previously installed the nvidia
> >>> proprietary driver from Negativo17 via dkms, and from what I can see
> >>> from the Xorg log, Xorg is loading that driver and the 
> >>> corresponding glx
> >>> module just before the message that Xorg can't find any display 
> >>> devices
> >>> to use.
> >>>
> >>> I also checked the xorg.conf file and it specifies to use the nvidia
> >>> driver, should I change it to the above driver or is the above driver
> >>> unique to Wayland?
> >> The driver has nothing to do with Wayland as such. Clearly an Nvidia
> >> driver isn't going to work with a non-Nvidia GPU, which is what your VM
> >> has. If you're loading the Nvidia driver anyway, this may be the source
> >> of the problem. Remove the Nvidia stuff and try again.
> >>
> > Kernel driver in use: vmwgfx
> >
> > vmwgfx is VMWare guest GL driver
> >
> > If it were nVidia it would read
> >
> > Kernel driver in use: nvidia
>
>  I have tried removing the nvidia entries from the device group in 
>  xorg.conf, and, also specifying driver "vmware" instead of "nvidia",
>
>  and in both cases Gnome and KDE can be started with Xorg. In both 
>  cases though they start with the wrong screen resolution relative to 
>  the resolution that the vmware player is using. Gnome under Wayland is 
>  capable of re-setting its resolution to match that of the vmware 
>  player when maximizing the player, but KDE is not capable of doing so 
>  under Wayland. I might have to play around with the resolution 
>  configuration parameters to try to get Xorg to set its resolution to 
>  match vmware's. 
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 640x480, but the display configuration facility 
including 1600x844 as one of the resolutions it now provided, which then 
switched KDE into the desired resolution.


Section "Monitor"
     Identifier     "Monitor0"
     VendorName     "Unknown"
     ModelName      "Unknown"
     # HorizSync       28.0 - 33.0
     # VertRefresh     43.0 - 72.0
     Modeline       "1600x844_60.00"  110.75  1600 1696 1856 2112 844 
847 857 876 -hsync +vsync
     Option         "PreferredMode" "1600x844_60.00"
     Option         "DPMS"
EndSection


regards,

Steve

>
>
> regards,
>
> Steve
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Patrick O'Callaghan]

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 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".
>  > > > > There will be a line with "Kernel driver in use:".
>  > > > > 
>  > > > "lspci -v" gives me the following output:
>  > > > 
>  > > > 
>  > > > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00
>  > > > [VGA controller])
>  > > >           Subsystem: VMware SVGA II Adapter
>  > > >           Flags: bus master, medium devsel, latency 64, IRQ 16
>  > > >           I/O ports at 1070 [size=16]
>  > > >           Memory at e8000000 (32-bit, prefetchable) [size=128M]
>  > > >           Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
>  > > >           [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
>  > > >           Capabilities: <access denied>
>  > > >           Kernel driver in use: vmwgfx
>  > > >           Kernel modules: vmwgfx
>  > > > 
>  > > > This output is under Wayland. I have previously installed the nvidia
>  > > > proprietary driver from Negativo17 via dkms, and from what I can see
>  > > > from the Xorg log, Xorg is loading that driver and the corresponding glx
>  > > > module just before the message that Xorg can't find any display
> devices
>  > > > to use.
>  > > > 
>  > > > I also checked the xorg.conf file and it specifies to use the nvidia
>  > > > driver, should I change it to the above driver or is the above driver
>  > > > unique to Wayland?
>  > > The driver has nothing to do with Wayland as such. Clearly an Nvidia
>  > > driver isn't going to work with a non-Nvidia GPU, which is what your VM
>  > > has. If you're loading the Nvidia driver anyway, this may be the source
>  > > of the problem. Remove the Nvidia stuff and try again.
>  > > 
>  > Kernel driver in use: vmwgfx
>  > 
>  > vmwgfx is VMWare guest GL driver
>  > 
>  > If it were nVidia it would read
>  > 
>  > Kernel driver in use: nvidia
>  
>  I have tried removing the nvidia entries from the device group in 
>  xorg.conf, and, also specifying driver "vmware" instead of "nvidia",
> and 
>  in both cases Gnome and KDE can be started with Xorg. 
I would uninstall the Nvidia support completely to be on the safe side
(i.e. remove the package or at least blacklist the kernel module), but
that may not be necessary.

>  In both cases 
>  though they start with the wrong screen resolution relative to the 
>  resolution that the vmware player is using. Gnome under Wayland is 
>  capable of re-setting its resolution to match that of the vmware player 
>  when maximizing the player, but KDE is not capable of doing so under 
>  Wayland. I might have to play around with the resolution configuration 
>  parameters to try to get Xorg to set its resolution to match vmware's. 
I use KDE under X as currently Wayland support for KDE is running
behind Gnome. You may want to ask on the KDE list for more information.

poc

[Patrick O'Callaghan]

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 640x480, but the display configuration facility 
>  including 1600x844 as one of the resolutions it now provided, which then 
>  switched KDE into the desired resolution.
>  
>  
>  Section "Monitor"
>       Identifier     "Monitor0"
>       VendorName     "Unknown"
>       ModelName      "Unknown"
>       # HorizSync       28.0 - 33.0
>       # VertRefresh     43.0 - 72.0
>       Modeline       "1600x844_60.00"  110.75  1600 1696 1856 2112 844 
>  847 857 876 -hsync +vsync
>       Option         "PreferredMode" "1600x844_60.00"
>       Option         "DPMS"
>  EndSection 
Glad it worked out.

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 hassle to set up and depends on certain features of
your motherboard and BIOS, but I use it to run Windows games and it
works very well.

poc

[Stephen Morris]

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 resolution of 1600x844,
> > instead starting at 640x480, but the display configuration facility
> > including 1600x844 as one of the resolutions it now provided, which then
> > switched KDE into the desired resolution.
> >
> >
> > Section "Monitor"
> >       Identifier     "Monitor0"
> >       VendorName     "Unknown"
> >       ModelName      "Unknown"
> >       # HorizSync       28.0 - 33.0
> >       # VertRefresh     43.0 - 72.0
> >       Modeline       "1600x844_60.00"  110.75  1600 1696 1856 2112 844
> > 847 857 876 -hsync +vsync
> >       Option         "PreferredMode" "1600x844_60.00"
> >       Option         "DPMS"
> > EndSection
>  Glad it worked out.
>
>  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 hassle to set up and depends on certain features of
>  your motherboard and BIOS, but I use it to run Windows games and it
>  works very well. 
I orginally wanted to install Fedora as my main operating system, with 
Win 10 (for running games) and Ubuntu running in VM's under that, but 
the live cd installer not being able to see any devices with the bios 
running in raid mode put paid to that. But in preparation for doing that 
I googled graphics hardware acceleration in both vmware and virtualbox 
to decide which I would use. Virtualbox said it provided 3D hardware 
acceleration if you downloaded its graphic tools, whereas vmware said it 
provided 3D acceleration via a config setting as long as you used the 
appropriate video driver, which I took to mean I could use my standard 
Windows Nvidia Proprietary driver. My assumption that I could use the 
Linux nvidia driver the same way I thought the windows driver could be 
used seems to be misfounded.


regards,

Steve


>
> poc
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Stephen Morris]

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/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".
> >>>>> There will be a line with "Kernel driver in use:".
> >>>>>
> >>>> "lspci -v" gives me the following output:
> >>>>
> >>>>
> >>>> 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00
> >>>> [VGA controller])
> >>>>            Subsystem: VMware SVGA II Adapter
> >>>>            Flags: bus master, medium devsel, latency 64, IRQ 16
> >>>>            I/O ports at 1070 [size=16]
> >>>>            Memory at e8000000 (32-bit, prefetchable) [size=128M]
> >>>>            Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
> >>>>            [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
> >>>>            Capabilities: <access denied>
> >>>>            Kernel driver in use: vmwgfx
> >>>>            Kernel modules: vmwgfx
> >>>>
> >>>> This output is under Wayland. I have previously installed the nvidia
> >>>> proprietary driver from Negativo17 via dkms, and from what I can see
> >>>> from the Xorg log, Xorg is loading that driver and the corresponding glx
> >>>> module just before the message that Xorg can't find any display
> devices
> >>>> to use.
> >>>>
> >>>> I also checked the xorg.conf file and it specifies to use the nvidia
> >>>> driver, should I change it to the above driver or is the above driver
> >>>> unique to Wayland?
> >>> The driver has nothing to do with Wayland as such. Clearly an Nvidia
> >>> driver isn't going to work with a non-Nvidia GPU, which is what your VM
> >>> has. If you're loading the Nvidia driver anyway, this may be the source
> >>> of the problem. Remove the Nvidia stuff and try again.
> >>>
> >> Kernel driver in use: vmwgfx
> >>
> >> vmwgfx is VMWare guest GL driver
> >>
> >> If it were nVidia it would read
> >>
> >> Kernel driver in use: nvidia
> > I have tried removing the nvidia entries from the device group in
> > xorg.conf, and, also specifying driver "vmware" instead of
> "nvidia", and
> > in both cases Gnome and KDE can be started with Xorg.
>  I would uninstall the Nvidia support completely to be on the safe side
>  (i.e. remove the package or at least blacklist the kernel module), but
>  that may not be necessary.
>
> > In both cases
> > though they start with the wrong screen resolution relative to the
> > resolution that the vmware player is using. Gnome under Wayland is
> > capable of re-setting its resolution to match that of the vmware player
> > when maximizing the player, but KDE is not capable of doing so under
> > Wayland. I might have to play around with the resolution configuration
> > parameters to try to get Xorg to set its resolution to match vmware's.
>  I use KDE under X as currently Wayland support for KDE is running
>  behind Gnome. You may want to ask on the KDE list for more information. 
Thanks Patrick, I'm still deciding which way to go, as I'm a bit wary of 
Wayland having had a bad experience with the Gnome/Wayland combination 
in F28.


regards,

Steve


>
> poc
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Patrick O'Callaghan]

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 hassle to set up and depends on certain features of
>  > your motherboard and BIOS, but I use it to run Windows games and it
>  > works very well.
>  
>  I orginally wanted to install Fedora as my main operating system, with 
>  Win 10 (for running games) and Ubuntu running in VM's under that, but 
>  the live cd installer not being able to see any devices with the bios 
>  running in raid mode put paid to that. But in preparation for doing that 
>  I googled graphics hardware acceleration in both vmware and virtualbox 
>  to decide which I would use. Virtualbox said it provided 3D hardware 
>  acceleration if you downloaded its graphic tools, whereas vmware said it 
>  provided 3D acceleration via a config setting as long as you used the 
>  appropriate video driver, which I took to mean I could use my standard 
>  Windows Nvidia Proprietary driver. My assumption that I could use the 
>  Linux nvidia driver the same way I thought the windows driver could be 
>  used seems to be misfounded. 
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 Linux, so Linux uses your motherboard's IGP (internal
graphics processor) and the VM has direct physical access to the faster
GPU. The GPU cannot be shared between the host and guest systems (or
between various guests, in case you're wondering). Being able to do
this depends on your hardware setup. Here's a Quora article I wrote a
while back which may help:

https://www.quora.com/Is-it-possible-to-run-all-Windows-games-on-Fedora-L...

poc

[Stephen Morris]

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 on KVM/QEMU.
> >> It's something of a hassle to set up and depends on certain features of
> >> your motherboard and BIOS, but I use it to run Windows games and it
> >> works very well.
> > I orginally wanted to install Fedora as my main operating system, with
> > Win 10 (for running games) and Ubuntu running in VM's under that, but
> > the live cd installer not being able to see any devices with the bios
> > running in raid mode put paid to that. But in preparation for doing that
> > I googled graphics hardware acceleration in both vmware and virtualbox
> > to decide which I would use. Virtualbox said it provided 3D hardware
> > acceleration if you downloaded its graphic tools, whereas vmware said it
> > provided 3D acceleration via a config setting as long as you used the
> > appropriate video driver, which I took to mean I could use my standard
> > Windows Nvidia Proprietary driver. My assumption that I could use the
> > Linux nvidia driver the same way I thought the windows driver could be
> > used seems to be misfounded.
>  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 Linux, so Linux uses your motherboard's IGP (internal
>  graphics processor) and the VM has direct physical access to the faster
>  GPU. The GPU cannot be shared between the host and guest systems (or
>  between various guests, in case you're wondering). Being able to do
>  this depends on your hardware setup. Here's a Quora article I wrote a
>  while back which may help:
>
>  https://www.quora.com/Is-it-possible-to-run-all-Windows-games-on-Fedora-L... 
Thanks Patrick, I read that article and it was very enlightening. From 
what you said I may have had a lot of difficulty doing what I wanted to do.


regards,

Steve


>
> poc
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Patrick O'Callaghan]

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 Linux, so Linux uses your motherboard's IGP (internal
>  > graphics processor) and the VM has direct physical access to the faster
>  > GPU. The GPU cannot be shared between the host and guest systems (or
>  > between various guests, in case you're wondering). Being able to do
>  > this depends on your hardware setup. Here's a Quora article I wrote a
>  > while back which may help:
>  > 
>  > https://www.quora.com/Is-it-possible-to-run-all-Windows-games-on-Fedora-L...
>  
>  Thanks Patrick, I read that article and it was very enlightening. From 
>  what you said I may have had a lot of difficulty doing what I wanted to do. 
It's definitely a project. I reckon it took me several days to get it
all working (mostly in figuring out the low-level hardware stuff but
others might find this easier), with several tune-ups later on to improve performance.

poc