External Monitor Nvidia Driver & Resolution Issues

Getting your soundcard to work, using Debian on non-i386 hardware, etc

External Monitor Nvidia Driver & Resolution Issues

Postby trabako » 2019-05-18 09:01

Hello. Having tried other Debian-based distros, I thought I should try Debian as my last chance before buying another laptop.

My laptop's screen (https://www.cnet.com/products/acer-aspire-5684wlmi-15-4-core-2-duo-t5600-win-xp-mce-2005-1-gb-ram-120-gb-hdd-series/) stopped working (burned) so I connected an external one (https://www.cnet.com/products/dell-professional-p190s-lcd-monitor-19-series/) through VGA Cable.

Code: Select all
inxi -Fxz
System:    Host: robal Kernel: 4.9.0-9-686-pae i686 (32 bit gcc: 6.3.0) Desktop: LXDE (Openbox 3.6.1)
           Distro: Debian GNU/Linux 9 (stretch)
Machine:   Device: laptop System: Acer product: Aspire 5680 v: V3.60
           Mobo: Acer model: Grapevine BIOS: Acer v: V3.60 date: 08/12/2008
CPU:       Dual core Intel Core2 T5600 (-MCP-) cache: 2048 KB
           flags: (lm nx pae sse sse2 sse3 ssse3 vmx) bmips: 7315
           clock speeds: max: 1833 MHz 1: 1333 MHz 2: 1333 MHz
Graphics:  Card: NVIDIA G73M [GeForce Go 7600] bus-ID: 01:00.0
           Display Server: X.Org 1.19.2 drivers: vesa,nouveau (unloaded: modesetting,fbdev)
           Resolution: 1280x1024@0.00hz
           GLX Renderer: N/A GLX Version: N/A Direct Rendering: N/A
Audio:     Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.9.0-9-686-pae
Network:   Card-1: Broadcom Limited NetLink BCM5789 Gigabit Ethernet PCI Express
           driver: tg3 v: 3.137 bus-ID: 04:00.0
           IF: enp4s0 state: down mac: <filter>
           Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection
           driver: iwl3945 v: in-tree:s bus-ID: 05:00.0
           IF: wlp5s0 state: up mac: <filter>
Drives:    HDD Total Size: 120.0GB (7.2% used)
           ID-1: /dev/sda model: Hitachi_HTS54161 size: 120.0GB temp: 40C
Partition: ID-1: / size: 32G used: 3.6G (12%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 75G used: 685M (1%) fs: ext4 dev: /dev/sda3
           ID-3: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 41.0C mobo: 41.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 139 Uptime: 1:11 Memory: 744.8/2018.1MB Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121) inxi: 2.3.5



After a fresh install of Debian 9, I have problem with color stripes when I open a folder or a program (Firefox) and freezing when playing videos... I think it is due to vesa driver used. I have blacklisted nouveau driver in my grub file because of dmesg errors.

The Nvidia driver for my card (GeForce Go 7600) is nvidia-legacy-304xx. I installed it following the official instructions
https://wiki.debian.org/NvidiaGraphicsD ... cy_GPUs.29

and I also tried Len E. thread suggestions (install nvidia-legacy-304xx-kernel-dkms through synaptic)
viewtopic.php?f=5&t=142001

On both occasions, I can not log in, I get a blank screen, only tty (Ctrl+Alt+F1). This is because of lightdm: failed to start. My lightdm.conf file:

Code: Select all
cat /etc/lightdm/lightdm.conf
#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
# backup-logs = True to move add a .old suffix to old log files when opening new ones
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#logind-check-graphical=false
#log-directory=/var/log/lightdm
#run-directory=/var/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters
#backup-logs=true

#
# Seat configuration
#
# Seat configuration is matched against the seat name glob in the section, for example:
# [Seat:*] matches all seats and is applied first.
# [Seat:seat0] matches the seat named "seat0".
# [Seat:seat-thin-client*] matches all seats that have names that start with "seat-thin-client".
#
# type = Seat type (xlocal, xremote, unity)
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option)
# xserver-config = Config file to pass to X server
# xserver-layout = Layout to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[Seat:*]
#type=xlocal
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin
#pam-greeter-service=lightdm-greeter
#xserver-command=X
#xmir-command=Xmir
#xserver-config=
#xserver-layout=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#unity-compositor-command=unity-system-compositor
#unity-compositor-timeout=60
greeter-session=lightdm-gtk-greeter
greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-user-switching=true
#allow-guest=true
#guest-session=
#session-wrapper=lightdm-session
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=
#exit-on-failure=false

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# listen-address = Host/address to listen for XDMCP connections (use all addresses if not present)
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
# hostname = Hostname to report to XDMCP clients (defaults to system hostname if unset)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn.  Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#listen-address=
#key=
#hostname=

#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# listen-address = Host/address to listen for VNC connections (use all addresses if not present)
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#listen-address=
#width=1024
#height=768
#depth=8

logind-check-graphical=true


In order to provide more logs (Xorg.log , lightdm.log etc.) I have to run again the installation process of nvidia driver.


Let me ask the following questions:

1) Is it possible to "force" the loading of another driver except vesa, nouveau? By creating a monitor.conf file in /etc/X11/xorg.conf.d/ ...

2) Regarding nvidia-legacy-304xx-driver: is there another way to successfully install it? The blacklist files in /etc/modprobe.d/ were created after the installation. I also created an 20-nvidia.conf file as described in Debian NvidiaGraphicsDrivers Post.

Looking forward to your help-suggestions!
trabako
 
Posts: 1
Joined: 2019-05-14 18:53

Re: External Monitor Nvidia Driver & Resolution Issues

Postby ruwolf » 2019-07-01 04:14

I know how to force load graphics driver:
Give it to config file and uninstall all other graphics drivers.
Of course, when it fails, you will have not default drivers remaining, so X will not start at all...

P.S.
In /var/log/Xorg.0.log you can find all errors and their causes...
I do not understand your sentence:
In order to provide more logs (Xorg.log , lightdm.log etc.) I have to run again the installation process of nvidia driver.
It is automatically removed after start of lightdm fails?
User avatar
ruwolf
 
Posts: 365
Joined: 2008-02-18 05:04
Location: Slovakia, Banovce nad Bebravou, Matice slovenskej 1260/4-7

Re: External Monitor Nvidia Driver & Resolution Issues

Postby Head_on_a_Stick » 2019-07-01 17:33

trabako wrote:I have blacklisted nouveau driver in my grub file because of dmesg errors.

But did nouveau actually work? If not did you try installing the firmware-misc-nonfree package?

trabako wrote:In order to provide more logs (Xorg.log , lightdm.log etc.) I have to run again the installation process of nvidia driver.

Can't you just login on a console screen and use pastebinit to generate a URL linking to the logs and then post that here?

trabako wrote:I also created an 20-nvidia.conf file as described in Debian NvidiaGraphicsDrivers Post.

An X.org configuration file is no longer needed for the proprietary NVIDIA drivers, apparently.
User avatar
Head_on_a_Stick
 
Posts: 10346
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: External Monitor Nvidia Driver & Resolution Issues

Postby trab » 2019-07-05 16:21

I'm sorry for my late reply. I hoped that someone could give me some advice. I'd like to thank you for your help.

The current situation is that the vesa driver is loaded:

Code: Select all
# inxi -Gxx
Graphics:  Card: NVIDIA G73M [GeForce Go 7600] bus-ID: 01:00.0 chip-ID: 10de:0398
           Display Server: X.org 1.19.2 drivers: vesa,nouveau (unloaded: modesetting,fbdev)
           tty size: 140x51 Advanced Data: N/A for root


I've also removed the blacklisting of nouveau driver in my grub file.


1) Regarding ruwolf's post:

In order to test his suggestion, I created the 11-monitor.conf file in
Code: Select all
/etc/X11/xorg.conf.d/


Code: Select all
Section "Monitor"
   Identifier    "Monitor0"
   HorizSync       30.0 - 81.0      
   VertRefresh     56.0 - 76.0
   Modeline "1280x1024_59.89"  108.00  1280 1368 1496 1712  1024 1027 1034 1063 -HSync +VSync
EndSection

Section "Device"
   Identifier   "Device0"
    Driver   "nouveau"
   BusID  "PCI:1:0:0"
   Option "Monitor-default" "Monitor0"
EndSection

Section "Screen"
   Identifier   "Screen0"
   Device   "Device0"
   Monitor   "Monitor0"
   DefaultDepth   16
   SubSection     "Display"
      Depth       16
      Modes "1280x1024_59.89"
   EndSubSection
EndSection



But after restart, I can not log in, I get a blank screen...


2) Regarding Head_on_a_Stick post:

As I've mentioned in my first post, I followed these instructions:

https://wiki.debian.org/NvidiaGraphicsDrivers#Version_304.135_.28legacy_GPUs.29

The firmware-misc-nonfree package is installed

Code: Select all
# apt-get install firmware-misc-nonfree
Reading package lists... Done
Building dependency tree       
Reading state information... Done
firmware-misc-nonfree is already the newest version (20190114-1~bpo9+2).
firmware-misc-nonfree set to manually installed.



Please advise me which installation procedure of Nvidia legacy driver I should follow and which logs you want to post in case of failure.

Thank you very much!
trab
 
Posts: 1
Joined: 2019-04-10 09:50


Return to Hardware

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable