Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing

2024-06-30 Thread Dale
Michael wrote:
> This is good! :D
> Edit the section below by adding the PreferredMode line:
>
> Section "Monitor"
> Identifier "Monitor0"
> VendorName "Unknown"
> ModelName  "LG Electronics W2253"
> HorizSync   30.0 - 83.0
> VertRefresh 56.0 - 61.0
> Option "PreferredMode"   "1920x1080_60.00"
> Option "DPMS"
> EndSection
>
> Save it, then check if you get a consistent result when you restart the DM, 
> or 
> reboot.
>
> If it is still playing up you need to show the Xorg.0.log while the monitor 
> is 
> working with the nvidia driver, to see which Modeline it uses and add this in 
> the "Monitor" section too, above the "PreferredMode" entry.
>
> If none of this works reliably, then you have to capture the EDID table while 
> the monitor is working, save it in a file and set nvidia-settings to use it 
> hereafter.  However, if you will NOT be using this monitor for much longer 
> this would be an exercise only to make you feel good for beating it into 
> submission!  LOL!

OK.  First time, it worked.  Second time, it came up but in low res. 
Plasma was working to, both times.  So, I opened the Nvidia GUI and told
it to safe a new config with it in hi res mostly just to see what it
would add if anything.  It did.  The only change I could see was it
added metamodes options like this:

Section "Screen"

# Removed Option "metamodes" "nvidia-auto-select +0+0"
    Identifier "Screen0"
    Device "Device0"
    Monitor    "Monitor0"
    DefaultDepth    24
    Option "Stereo" "0"
    Option "nvidiaXineramaInfoOrder" "DP-3"
    Option "metamodes" "1920x1080 +0+0"
#    Option "metamodes" "1920x1080 +0+0; 1024x768_60 +0+0"
    Option "SLI" "Off"
    Option "MultiGPU" "Off"
    Option "BaseMosaic" "off"
    SubSection "Display"
    Depth   24
    EndSubSection
EndSection


As you can see, I removed the low res part, don't want that anyway, and
it seems to work more often but still fails a lot.  So, I removed the
metamodes Nvidia added.  Then it didn't come up at all, sddm or
anything, when I restarted DM.  I thought it adding your setting to
another section might help.  Guess not.  With the following removed, it
seems to do a little better but still can't depend on it to work.

Section "Screen"
#    Option "nvidiaXineramaInfoOrder" "DP-3"
#    Option "metamodes" "1920x1080 +0+0"
#    Option "metamodes" "1920x1080 +0+0; 1024x768_60 +0+0"


Basically, it is doing like it always has.  Most of the time, it doesn't
work.  Sometimes it does.  To be honest tho, I still wonder if it even
reads the file.  When I change something, I'd expect something
different.  Generally, it doesn't seem to affect anything unless I
reboot completely.  Sometimes I'm not sure it does then either.  So, I
think this old monitor just has a issue.  Maybe I need to rebuild some
more of the power supply or something in case it is providing bad power
to the parts that talks to the puter.  Either way, if the new one works,
I just don't think this old monitor is going to work correctly no matter
what we throw at it. 

I will saw this, we threw the kitchen sink at it.  I think this is one
of the longest threads I've seen in a long while.  o_O 

Dale

:-) 

P. S.  Monitor updated.  Now it says tomorrow.  It's in the right place
to do so.  It's at the Memphis hub.  Usually, it comes from there to the
local distribution point and on the truck.  They sometimes deliver by
noon.  Could be a little late given it is Monday. 


Re: [gentoo-user] bash: genfun_has_readline

2024-06-30 Thread Peter Humphrey
On Sunday, 30 June 2024 18:51:20 BST David M. Fellows wrote:
> >Hello list,
> >
> >I'm seeing this every time I chroot into my rescue system:
> >
> ># chroot /mnt/rescue /bin/bash
> >bash: genfun_has_readline: command not found
> >
> >Google results suggest that the genfun is defined in the new version of
> >bashrc, but it isn't on any of my systems, even one ~amd64.
> >
> >The same thing happened when I started a new build from stage-3, when I
> >chrooted into the nascent system.
> >
> >Clues, anyone?
> 
> https://bugs.gentoo.org/935016
> 
> May have relevant information.

Thanks, but it doesn't help. What it says doesn't apply here.

-- 
Regards,
Peter.






Re: [gentoo-user] bash: genfun_has_readline

2024-06-30 Thread David M. Fellows
>Hello list,
>
>I'm seeing this every time I chroot into my rescue system:
>
># chroot /mnt/rescue /bin/bash
>bash: genfun_has_readline: command not found
>
>Google results suggest that the genfun is defined in the new version of 
>bashrc, 
>but it isn't on any of my systems, even one ~amd64.
>
>The same thing happened when I started a new build from stage-3, when I 
>chrooted into the nascent system.
>
>Clues, anyone?

https://bugs.gentoo.org/935016

May have relevant information.

DaveF
>
>-- 
>Regards,
>Peter.
>
>
>
>



[gentoo-user] bash: genfun_has_readline

2024-06-30 Thread Peter Humphrey
Hello list,

I'm seeing this every time I chroot into my rescue system:

# chroot /mnt/rescue /bin/bash
bash: genfun_has_readline: command not found

Google results suggest that the genfun is defined in the new version of bashrc, 
but it isn't on any of my systems, even one ~amd64.

The same thing happened when I started a new build from stage-3, when I 
chrooted into the nascent system.

Clues, anyone?

-- 
Regards,
Peter.






Re: [gentoo-user] cinnamon-screensaver issue

2024-06-30 Thread Jacques Montier
Le dim. 30 juin 2024 à 15:03, Eli Schwartz  a écrit :

> On 6/30/24 6:57 AM, Jacques Montier wrote:
> > Hello all,
> >
> > In the cinnamon xscreensaver preferences, time before the xscreensaver
> > starts is set to 5min.
> > After those 5 min, instead of the screensaver, all my working
> applications
> > stopped, the cinnamon xsession exit, and i just get the sddm screen for
> > logging...
> >
> > Manually launching with cinnamon-screensaver-command, it works fine.
> >
> > I really don't know what's going on.
> >
> > Attached journalctl extract.
> >
> > Installed version cinnamon :
> > gnome-extra/cinnamon-6.0.4
> > gnome-extra/cinnamon-screensaver-6.0.3
> >
> > Thanks a lot for your help.
>
>
> Waiting for https://bugs.gentoo.org/935054 to stabilize. Consider
> package.accept_keywords for cinnamon-session in the meantime.
>
> See also https://github.com/gentoo/gentoo/pull/36989
>
>
> --
> Eli Schwartz
>


Hello Eli,

I upgraded to (~) cinnamon-session-6.0.4 and it works fine.

Thanks very much.

Cheers,

--
Jacques


Re: [gentoo-user] cinnamon-screensaver issue

2024-06-30 Thread Eli Schwartz
On 6/30/24 6:57 AM, Jacques Montier wrote:
> Hello all,
> 
> In the cinnamon xscreensaver preferences, time before the xscreensaver
> starts is set to 5min.
> After those 5 min, instead of the screensaver, all my working applications
> stopped, the cinnamon xsession exit, and i just get the sddm screen for
> logging...
> 
> Manually launching with cinnamon-screensaver-command, it works fine.
> 
> I really don't know what's going on.
> 
> Attached journalctl extract.
> 
> Installed version cinnamon :
> gnome-extra/cinnamon-6.0.4
> gnome-extra/cinnamon-screensaver-6.0.3
> 
> Thanks a lot for your help.


Waiting for https://bugs.gentoo.org/935054 to stabilize. Consider
package.accept_keywords for cinnamon-session in the meantime.

See also https://github.com/gentoo/gentoo/pull/36989


-- 
Eli Schwartz


OpenPGP_0x84818A6819AF4A9B.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


[gentoo-user] cinnamon-screensaver issue

2024-06-30 Thread Jacques Montier
Hello all,

In the cinnamon xscreensaver preferences, time before the xscreensaver
starts is set to 5min.
After those 5 min, instead of the screensaver, all my working applications
stopped, the cinnamon xsession exit, and i just get the sddm screen for
logging...

Manually launching with cinnamon-screensaver-command, it works fine.

I really don't know what's going on.

Attached journalctl extract.

Installed version cinnamon :
gnome-extra/cinnamon-6.0.4
gnome-extra/cinnamon-screensaver-6.0.3

Thanks a lot for your help.

Cheers,


*--*
*Jacques*
juin 29 20:52:12 GentooLinux org.cinnamon.ScreenSaver[3569]: Loading 
AccountsService
juin 29 20:52:12 GentooLinux org.cinnamon.ScreenSaver[3569]: Fractional scaling 
active: False
juin 29 20:52:12 GentooLinux cinnamon-killer-daemon[3590]: Bound Cinnamon 
restart to Escape.
juin 29 20:52:12 GentooLinux org.cinnamon.ScreenSaver[3569]: Trying to connect 
to logind...
juin 29 20:52:12 GentooLinux dbus-daemon[1072]: [session uid=1000 pid=1072 
pidfd=5] Successfully activated service 'org.cinnamon.ScreenSaver'
juin 29 20:52:12 GentooLinux org.cinnamon.ScreenSaver[3569]: Starting 
screensaver...
juin 29 20:52:12 GentooLinux dbus-daemon[1072]: [session uid=1000 pid=1072 
pidfd=5] Activating service name='org.cinnamon.CalendarServer' requested by 
':1.188' (uid=1000 pi>
juin 29 20:52:12 GentooLinux NetworkManager[929]:   [1719687132.4846] 
agent-manager: agent[79132a7687efe89c,:1.346/org.freedesktop.nm-applet/1000]: 
agent registered
juin 29 20:52:12 GentooLinux org.cinnamon.ScreenSaver[3569]: Cinnamon 
Screensaver support not found in current theme - adding some...
juin 29 20:52:12 GentooLinux cinnamon-session[3388]: WARNING: t+2.29526s: 
Detected that screensaver has appeared on the bus
juin 29 20:52:12 GentooLinux org.cinnamon.ScreenSaver[3569]: AccountsService 
ready
juin 29 20:52:12 GentooLinux org.cinnamon.ScreenSaver[3569]: Successfully using 
logind
juin 29 20:52:12 GentooLinux dbus-daemon[1072]: [session uid=1000 pid=1072 
pidfd=5] Successfully activated service 'org.cinnamon.CalendarServer'
juin 29 20:52:20 GentooLinux systemd[1]: Stopping User Manager for UID 219...
juin 29 20:52:20 GentooLinux systemd[3253]: Activating special unit Exit the 
Session...
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped target Main User Target.
juin 29 20:52:20 GentooLinux wireplumber[3276]: m-dbus-connection: 
 DBus connection closed: Underlying GIOStream 
returned 0 bytes on an asy>
juin 29 20:52:20 GentooLinux gvfsd[3301]: A connection to the bus can't be made
juin 29 20:52:20 GentooLinux systemd[3253]: Stopping D-Bus User Message Bus...
juin 29 20:52:20 GentooLinux wireplumber[3276]: m-dbus-connection: 
 Trying to reconnect after core sync
juin 29 20:52:20 GentooLinux systemd[3253]: Stopping Virtual filesystem 
service...
juin 29 20:52:20 GentooLinux systemd[3253]: Stopping PipeWire PulseAudio...
juin 29 20:52:20 GentooLinux systemd[3253]: Stopping sandboxed app permission 
store...
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped D-Bus User Message Bus.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped Virtual filesystem service.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped PipeWire PulseAudio.
juin 29 20:52:20 GentooLinux systemd[3253]: xdg-permission-store.service: Main 
process exited, code=exited, status=1/FAILURE
juin 29 20:52:20 GentooLinux systemd[3253]: xdg-permission-store.service: 
Failed with result 'exit-code'.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped sandboxed app permission 
store.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopping Multimedia Service Session 
Manager...
juin 29 20:52:20 GentooLinux wireplumber[3276]: wireplumber: stopped by signal: 
Complété
juin 29 20:52:20 GentooLinux wireplumber[3276]: wireplumber: disconnected from 
pipewire
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped Multimedia Service Session 
Manager.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopping PipeWire Multimedia 
Service...
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped PipeWire Multimedia Service.
juin 29 20:52:20 GentooLinux systemd[3253]: Removed slice User Core Session 
Slice.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped target Basic System.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped target Paths.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped target Sockets.
juin 29 20:52:20 GentooLinux systemd[3253]: Stopped target Timers.
juin 29 20:52:20 GentooLinux systemd[3253]: Closed D-Bus User Message Bus 
Socket.
juin 29 20:52:20 GentooLinux systemd[3253]: Closed PipeWire PulseAudio.
juin 29 20:52:20 GentooLinux systemd[3253]: Closed PipeWire Multimedia System 
Sockets.
juin 29 20:52:20 GentooLinux systemd[3253]: Removed slice User Application 
Slice.
juin 29 20:52:20 GentooLinux systemd[3253]: Reached target Shutdown.
juin 29 20:52:20 GentooLinux systemd[3253]: Finished Exit the Session.
juin 29 20:52:20 GentooLinux systemd[3253]: Reached target Exit the Session.
juin 29 20:52:20 GentooLinux (sd-pam)[3254]: 

Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing

2024-06-30 Thread Michael
On Sunday, 30 June 2024 10:36:16 BST Dale wrote:

> Here's a little update.  First, Kubuntu wiped my Gentoo install from
> being able to boot it.  I had to boot the Gentoo USB image, mount
> everything and reinstall grub/EFI stuff.  I got it back and now I can
> boot either one by selecting it in the BIOS. 
> 
> Second.  I decided to annoy the heck out of that thing.  I logged in
> over ssh and I kept restarting DM.  Took me several dozen tries but
> eventually I got KDE to come up, plasma and all.  I opened the Nvidia
> GUI and got it to save the xorg.conf file.  It's different but it has a
> lot of info now.

This is good!  :D

Edit the section below by adding the PreferredMode line:

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "LG Electronics W2253"
HorizSync   30.0 - 83.0
VertRefresh 56.0 - 61.0
Option "PreferredMode"   "1920x1080_60.00"
Option "DPMS"
EndSection

Save it, then check if you get a consistent result when you restart the DM, or 
reboot.

If it is still playing up you need to show the Xorg.0.log while the monitor is 
working with the nvidia driver, to see which Modeline it uses and add this in 
the "Monitor" section too, above the "PreferredMode" entry.

If none of this works reliably, then you have to capture the EDID table while 
the monitor is working, save it in a file and set nvidia-settings to use it 
hereafter.  However, if you will NOT be using this monitor for much longer 
this would be an exercise only to make you feel good for beating it into 
submission!  LOL!


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing

2024-06-30 Thread Dale
Dale wrote:
> Mark Knecht wrote:
>>
>>
>> He certainly does have his hands full!
>>
>> I'm confused. (a standard state of being for me...) I thought Dale
>> reported that
>> he installed Kubuntu on an SSD - or did we just talk about that idea
>> - and he
>> said all the port problems were ironed out with the open source driver.
>>
>> What he didn't report was if he installed the nvidia-drivers in
>> Kubuntu. I 
>> personally wouldn't write off the 'old monitor' until doing at least
>> that.
>>
>> sudo apt update
>> sudo apt upgrade
>>
>> ubuntu-drivers list
>> (make sure the video-card is found)
>>
>> sudo apt install nvidia-drivers-550
>> (assuming he has a Quadro P1000 from memory)
>>
>> reboot
>>
>> Shouldn't take more than 5-10 minutes to try. No real risk as 
>> he's going to blow away the Kubuntu install anyway.
>>
>
>
> I do have Kubuntu installed on a 2.5" SSD.  I wasn't sure how to
> install and switch to the Nvidia drivers.  That was on my todo list as
> soon as I had some time.  Thing is, the new monitor may get here
> first.  I just picked a whole gallon ice cream bucket packed full of
> basil.  It's soaking in the sink now.  Dehydrator comes next.  That
> takes at least a day to complete.  On the positive side, the house
> smells really good for a day or so.  LOL 
>
> I also thought of going to boot runlevel on my main rig while in a
> console, unplug the monitor hooked to my main rig now and plug it into
> the new rig.  Then boot and see what happens.  It might work.  It's a
> newer monitor and it's a Samsung instead of a LG.  If it did work, I
> could switch and switch to new monitor when it gets here.  I plan to
> use the old Dell rig to watch TV with while I switch.  I can use the
> backup drives for that.  Moving all these drives could take a while.  O_O
>
> At least now I have the commands needed to try it tho.  That helps.  :-D 
>
> Michael, I did try the settings you posted.  I thought I tried them
> and posted a reply.  I may have missed one tho.  This is a long
> thread.  This monitor has been a serious PITA.  :-@ 
>
> Back to the basil.  Glad my meds are working pretty good.  -_O
>
> Dale
>
> :-) :-) 


Here's a little update.  First, Kubuntu wiped my Gentoo install from
being able to boot it.  I had to boot the Gentoo USB image, mount
everything and reinstall grub/EFI stuff.  I got it back and now I can
boot either one by selecting it in the BIOS. 

Second.  I decided to annoy the heck out of that thing.  I logged in
over ssh and I kept restarting DM.  Took me several dozen tries but
eventually I got KDE to come up, plasma and all.  I opened the Nvidia
GUI and got it to save the xorg.conf file.  It's different but it has a
lot of info now.  Thing is, when I logged out and back in, same thing as
before.  Sometimes it doesn't work at all, sometimes it is the wrong
resolution or plasma doesn't start up or some other problem.  Since
email wraps things, I'm attaching the xorg.conf file it generated. 
Kinda nifty.  Some are like the info Micheal posted. 

I think at this point, I'm cutting the thing off until the new monitor
comes in.  I'm dreaming of hammers, shooting it and other things that
ain't good.  :/ 

Monitor is already about 100 miles from me at a FedEx hub.  I won't be
surprised if it comes in Monday.  It could be Tuesday tho.  They could
know it will take longer for some reason or other.  It's getting close
tho.  Yes, it is 4:30AM here.  Not a good night, yet.

Dale

:-)  :-) 
root@Gentoo-1 ~ # cat /etc/X11/xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 550.90.07

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 550.90.07

Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0" 0 0
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

# generated from data in "/etc/conf.d/gpm"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "LG Electronics W2253"
HorizSync   30.0 - 83.0
VertRefresh 56.0 - 61.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "Quadro P1000"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DP-3"
Option

Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing

2024-06-30 Thread Dale
Dale wrote:
> Mark Knecht wrote:
>>
>>
>> He certainly does have his hands full!
>>
>> I'm confused. (a standard state of being for me...) I thought Dale
>> reported that
>> he installed Kubuntu on an SSD - or did we just talk about that idea
>> - and he
>> said all the port problems were ironed out with the open source driver.
>>
>> What he didn't report was if he installed the nvidia-drivers in
>> Kubuntu. I 
>> personally wouldn't write off the 'old monitor' until doing at least
>> that.
>>
>> sudo apt update
>> sudo apt upgrade
>>
>> ubuntu-drivers list
>> (make sure the video-card is found)
>>
>> sudo apt install nvidia-drivers-550
>> (assuming he has a Quadro P1000 from memory)
>>
>> reboot
>>
>> Shouldn't take more than 5-10 minutes to try. No real risk as 
>> he's going to blow away the Kubuntu install anyway.
>>
>
>
> I do have Kubuntu installed on a 2.5" SSD.  I wasn't sure how to
> install and switch to the Nvidia drivers.  That was on my todo list as
> soon as I had some time.  Thing is, the new monitor may get here
> first.  I just picked a whole gallon ice cream bucket packed full of
> basil.  It's soaking in the sink now.  Dehydrator comes next.  That
> takes at least a day to complete.  On the positive side, the house
> smells really good for a day or so.  LOL 
>
> I also thought of going to boot runlevel on my main rig while in a
> console, unplug the monitor hooked to my main rig now and plug it into
> the new rig.  Then boot and see what happens.  It might work.  It's a
> newer monitor and it's a Samsung instead of a LG.  If it did work, I
> could switch and switch to new monitor when it gets here.  I plan to
> use the old Dell rig to watch TV with while I switch.  I can use the
> backup drives for that.  Moving all these drives could take a while.  O_O
>
> At least now I have the commands needed to try it tho.  That helps.  :-D 
>
> Michael, I did try the settings you posted.  I thought I tried them
> and posted a reply.  I may have missed one tho.  This is a long
> thread.  This monitor has been a serious PITA.  :-@ 
>
> Back to the basil.  Glad my meds are working pretty good.  -_O
>
> Dale
>
> :-) :-) 


Here's a little update.  First, Kubuntu wiped my Gentoo install from
being able to boot it.  I had to boot the Gentoo USB image, mount
everything and reinstall grub/EFI stuff.  I got it back and now I can
boot either one by selecting it in the BIOS. 

Second.  I decided to annoy the heck out of that thing.  I logged in
over ssh and I kept restarting DM.  Took me several dozen tries but
eventually I got KDE to come up, plasma and all.  I opened the Nvidia
GUI and got it to save the xorg.conf file.  It's different but it has a
lot of info now.  Thing is, when I logged out and back in, same thing as
before.  Sometimes it doesn't work at all, sometimes it is the wrong
resolution or plasma doesn't start up or some other problem.  Since
email wraps things, I'm attaching the xorg.conf file it generated. 
Kinda nifty.  Some are like the info Micheal posted. 

I think at this point, I'm cutting the thing off until the new monitor
comes in.  I'm dreaming of hammers, shooting it and other things that
ain't good.  :/ 

Monitor is already about 100 miles from me at a FedEx hub.  I won't be
surprised if it comes in Monday.  It could be Tuesday tho.  They could
know it will take longer for some reason or other.  It's getting close
tho. 

Dale

:-)  :-) 
root@Gentoo-1 ~ # cat /etc/X11/xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 550.90.07

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 550.90.07

Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0" 0 0
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

# generated from data in "/etc/conf.d/gpm"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "LG Electronics W2253"
HorizSync   30.0 - 83.0
VertRefresh 56.0 - 61.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "Quadro P1000"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DP-3"
Option "metamodes" "nvidia-auto-select +0+0"