Using old laptop with dumb frame buffer and external display

My 10 years old HP-Compac 8710w laptop has got some graphics failures with stripes and blinking disturbances on the TFT display already from boot screens to Gnome logni sessions. I Tested both booting Leap 15/nouveau and Win10.

I suspect the Nvidia Quadro FX 3600M graphics card is defect; or optionally/also the laptop TFT display. While 1920x1200 was its working resolution previously, now only 1280x1080 is found available with Gnome monitor or xrandr. And I haven’t succeeded so far to get VGA video output to a connected monitor, neither via the built-in VGA port nor via a docking station VGA port.

My question is if it is practically possible to get the hp8710w laptop to work with GUI via a possible internal “dumb frame buffer” (instead of the Nvidia GPU) and with a connected VGA monitor? If so, troubleshooting and setup prosedures will be welcome. I have no idea how to possibly disable a defect Nvidia card or if it has to be physically removed from the machine.

Thx

Possible, yes. Practical, depends on your definition of practical. You can append nomodeset to the kernel cmdline at the Grub menu to disable all competent X drivers except for the proprietary NVidia driver, which if not installed correctly can cause failures in several ways to prevent X from working at all. If you eradicate all proprietary driver components, the nomodeset parameter will force X to try to fall back to either of the crude fallback drivers, VESA or FBDEV, neither of which are capable of non-VESA modes, which means no 1920x1200 or any other widescreen mode. If the hardware is at fault, falling back to VESA or FBDEV is highly unlikely to be of any help. Odd stripes are a common indicator of various kinds of generally uncorrectable hardware fault. If you are capable of laptop R&R, reseating socketed or cabled components might turn out to solve your problem, but don’t expect it.

The kernel cmdline can be supplied with parameters to force an output on or off. e.g., video=LVDS-0:d video=VGA-0:e would force an LVDS output off and a VGA output on. To know the right parameters generally one needs X to have generated an Xorg.0.log that shows what they are, usually whether “connected” or “unconnected” (which the xf86-video-intel driver will not report). This gets complicated when there are both Intel and NVidia gfxchips onboard, so exactly what might help you help us depends on you correctly following NVidia driver removal instructions, and collecting hardware and installed software details. Besides the content of Xorg.0.log, useful information can come from various sources, including but not limited to:

inxi -Gxx
lspci -nnk | grep -EiA3 'vga|3d|display'
hwinfo --monitor
xrandr --listproviders

If xf86-video-intel is not installed, it might need to be installed to have a chance at the Intel gfx working acceptably, which it cannot do if nomodeset is an included cmdline parameter.

So, the place to start is probably to eradicate NVidia driver components and see if the Intel driver can work at least well enough to collect the hardware information needed to help us help you. It may well not without having Bumblebee installed as well.

Optimus as your 8710w appears to have can be quite complicated when all the hardware working as it should, worse when not.

Thank you for the feedback on this topic.

As background information, it is several years and openSUSE versions since I used the proprietary Nvidia driver to test higher resolution on an external dual-dvi connected monitor. But it became too cumbersome for each kernel update, so I continued with the default nouveau driver and the 1920x1200 resolution on this hp7810w, which has worked fine up to the graphics failure happened short time ago.

Yesterday I tried also to install the Nvidia proprietary driver again, but the result was even worser and I didn’t even get a gui login. So I reinstalled Leap 15 again to-day, first without using ‘nouvealu.modeset=0’ during the installation. The pros here was that some video arrived on the VGA connected external monitor, but some later during the installation both displays became unreadable with wild and different colors and flickering. So I returned to teinstall from start, now using ‘nouvealu.modeset=0’. This reminded me that I probably had to use this also first time I installed Leap 15 during the beta, before the graphics failure. The cons now was no video signal was received on the external display so far.

So comments to your reply.

I wonder if already fallback drivers for VESA or FBDEV might be in use, as the resolution as already mentioned is lowered to 1280x1024, and no others are available on the display settings ?

I searhed for Xorg.0.log, but cannot find any on the installation.

Below here follows output from the suggested commands and from some other variants for addtional information:


inxi -Gxx
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
Graphics: Card: NVIDIA G92GLM [Quadro FX 3600M]
bus-ID: 01:00.0 chip-ID: 10de:061c
Display Server: X.org 1.19.6 driver: N/A
tty size: 80x24 Advanced Data: N/A for root

inxi -Fz
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
System: Host: linux-iv5y Kernel: 4.12.14-lp150.11-default x86_64 bits: 64
Console: tty 0 Distro: openSUSE Leap 15.0
Machine: Device: laptop System: Hewlett-Packard product: HP Compaq 8710w v: F.0F serial: <filter>
Mobo: Hewlett-Packard model: 30C3 v: KBC Version 73.31 serial: N/A
BIOS: Hewlett-Packard v: 68MAD Ver. F.0F date: 11/25/2008
Battery C1FD: charge: 0.0 Wh 0.0% condition: 37.7/37.7 Wh (100%)
CPU: Dual core Intel Core2 Duo T9500 (-MCP-) cache: 6144 KB
clock speeds: max: 2601 MHz 1: 800 MHz 2: 2601 MHz
Graphics: Card: NVIDIA G92GLM [Quadro FX 3600M]
Display Server: X.org 1.19.6 driver: N/A
tty size: 80x24 Advanced Data: N/A for root
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller
driver: snd_hda_intel
Sound: ALSA v: k4.12.14-lp150.11-default
Network: Card-1: Intel 82566MM Gigabit Network Connection driver: e1000e
IF: eth0 state: down mac: <filter>
Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection
driver: iwl4965
IF: wlan0 state: up mac: <filter>
Drives: HDD Total Size: 175.8GB (40.5% used)
ID-1: /dev/sda model: INTEL_SSDSA2CW16 size: 160.0GB
ID-2: USB /dev/sdb model: DataTraveler_3.0 size: 15.7GB
Partition: ID-1: / size: 20G used: 5.3G (29%) fs: ext4 dev: /dev/sda5
ID-2: /home size: 40G used: 450M (2%) fs: ext4 dev: /dev/sda3
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 224 Uptime: 2:12 Memory: 1738.3/3874.8MB
Init: systemd runlevel: 5 Client: Shell (bash) inxi: 2.3.40

lspci -nnk | grep -EiA3 ‘vga|3d|display’
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92GLM [Quadro FX 3600M] [10de:061c] (rev a2)
Subsystem: NVIDIA Corporation Device [10de:0518]
Kernel modules: nouveau
02:06.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b9)


hwinfo --gfxcard | grep -e Device -e Driver
Device: pci 0x061c “G92GLM [Quadro FX 3600M]”
SubDevice: pci 0x0518
Driver Info #0:
Driver Status: nouveau is active
Driver Activation Cmd: “modprobe nouveau”

hwinfo --gfxcard
34: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.378]
Unique ID: VCu0.yk2KD4BD_+B
Parent ID: vSkL.QFfXZDqAgF5
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: “nVidia G92GLM [Quadro FX 3600M]”
Vendor: pci 0x10de “nVidia Corporation”
Device: pci 0x061c “G92GLM [Quadro FX 3600M]”
SubVendor: pci 0x10de “nVidia Corporation”
SubDevice: pci 0x0518
Revision: 0xa2
Memory Range: 0xe5000000-0xe5ffffff (rw,non-prefetchable)
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
Memory Range: 0xe6000000-0xe7ffffff (rw,non-prefetchable)
I/O Ports: 0x4000-0x4fff (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 10 (no events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: “pci:v000010DEd0000061Csv000010DEsd00000518bc03sc00i00”
Driver Info #0:
Driver Status: nouveau is active
Driver Activation Cmd: “modprobe nouveau”
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #31 (PCI bridge)

Primary display adapter: #34

hwinfo --monitor | grep Model
Model: “PHILIPS Philips 244E”
Model: “AUO LCD Monitor”

hwinfo --monitor
37: None 00.0: 10000 Monitor
[Created at monitor.97]
Unique ID: rdCR.o83XfZMO5h1
Hardware Class: monitor
Model: “PHILIPS Philips 244E”
Vendor: PHL “PHILIPS”
Device: eisa 0xc061 “Philips 244E”
Serial ID: “DL11047733014”
Resolution: 720x400@70Hz
Resolution: 640x480@60Hz
Resolution: 640x480@67Hz
Resolution: 640x480@72Hz
Resolution: 640x480@75Hz
Resolution: 800x600@56Hz
Resolution: 800x600@60Hz
Resolution: 800x600@72Hz
Resolution: 800x600@75Hz
Resolution: 832x624@75Hz
Resolution: 1024x768@60Hz
Resolution: 1024x768@70Hz
Resolution: 1024x768@75Hz
Resolution: 1280x1024@75Hz
Resolution: 1920x1080@60Hz
Resolution: 1280x720@60Hz
Resolution: 1280x1024@60Hz
Size: 531x299 mm
Year of Manufacture: 2010
Week of Manufacture: 47
Detailed Timings #0:
Resolution: 1920x1080
Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync
Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync
Frequencies: 148.50 MHz, 67.50 kHz, 60.00 Hz
Driver Info #0:
Max. Resolution: 1920x1080
Vert. Sync Range: 56-76 Hz
Hor. Sync Range: 30-83 kHz
Bandwidth: 148 MHz
Config Status: cfg=new, avail=yes, need=no, active=unknown

38: None 00.2: 10002 LCD Monitor
[Created at monitor.97]
Unique ID: aHB6.rzzshEJ1vV1
Hardware Class: monitor
Model: “AUO LCD Monitor”
Vendor: AUO “AUO”
Device: eisa 0x1188
Resolution: 1920x1200@60Hz
Size: 367x229 mm
Year of Manufacture: 2007
Week of Manufacture: 1
Detailed Timings #0:
Resolution: 1920x1200
Horizontal: 1920 1968 2000 2100 (+48 +80 +180) -hsync
Vertical: 1200 1203 1209 1246 (+3 +9 +46) -vsync
Frequencies: 157.00 MHz, 74.76 kHz, 60.00 Hz
Config Status: cfg=new, avail=yes, need=no, active=unknown

hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.459]
Unique ID: rdCR.2OAj6u66na7
Hardware Class: framebuffer
Model: “NVIDIA G92 Board - 398_501E”
Vendor: “NVIDIA Corporation”
Device: “G92 Board - 398_501E”
SubVendor: “NVIDIA”
SubDevice:
Revision: “Chip Rev”
Memory Size: 14 MB
Memory Range: 0x01000000-0x01dfffff (rw)
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+1280), 24 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0330: 320x200 (+320), 8 bits
Mode 0x0331: 320x400 (+320), 8 bits
Mode 0x0332: 320x400 (+640), 16 bits
Mode 0x0333: 320x400 (+1280), 24 bits
Mode 0x0334: 320x240 (+320), 8 bits
Mode 0x0335: 320x240 (+640), 16 bits
Mode 0x0336: 320x240 (+1280), 24 bits
Mode 0x033d: 640x400 (+1280), 16 bits
Mode 0x033e: 640x400 (+2560), 24 bits
Mode 0x0345: 1600x1200 (+1600), 8 bits
Mode 0x0346: 1600x1200 (+3200), 16 bits
Mode 0x0347: 1400x1050 (+1400), 8 bits
Mode 0x0348: 1400x1050 (+2800), 16 bits
Mode 0x0349: 1400x1050 (+5600), 24 bits
Mode 0x034a: 1600x1200 (+6400), 24 bits
Mode 0x0352: 2048x1536 (+8192), 24 bits
Mode 0x0360: 1280x800 (+1280), 8 bits
Mode 0x0361: 1280x800 (+5120), 24 bits
Mode 0x0362: 768x480 (+768), 8 bits
Mode 0x0364: 1440x900 (+1440), 8 bits
Mode 0x0365: 1440x900 (+5760), 24 bits
Mode 0x0368: 1680x1050 (+1680), 8 bits
Mode 0x0369: 1680x1050 (+6720), 24 bits
Mode 0x037c: 1920x1200 (+1920), 8 bits
Mode 0x037d: 1920x1200 (+7680), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown

xrandr --listproviders
xrandr: Failed to get size of gamma for output default
Providers: number : 0

xrandr --prop
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 1280 x 1024
default connected primary 1280x1024+0+0 0mm x 0mm
_MUTTER_PRESENTATION_OUTPUT: 0
1280x1024 77.00*

I would add I took a screenshot of the 8710w desktop with the bad display. Looking at it on another machine, the image was quite ok without disturbing visble stripes etc. This got me to think that if it possibly to get the video signal redirected to the external VGA connected monitor, maybe it will displayed as good there ??

If you don’t find Xorg.#.log in /var/log/ then look in /home/*/.local/share/xorg/ and /root/.local/share/xorg/. If still no luck, try

journalctl -e _COMM=Xorg.bin

If still nothing, X has never been run, or it/they have been deleted, or maybe you’ve only used Wayland and Wayland does logging differently that I’m not aware of.

Possibly so if the hardware breakdown is at or after the LVDS output instead of before. It could be the laptop display panel itself that is at fault.

Now it looks like the video graphics or display is gone complete wild, as nothing but artificial colors are displayed rolling over the TFT during startup. And I don’t get in touch with the machine as it doesn’t display anything to the VGA monitor or behaves like PC/workstation.

Regarding Xorg.0.log, I should just mentione this was a new Leap 15/Gnome re-installation from scratch, and I noticed there was no ‘Gnome on Xorg’ session available on the login selection menu as on my other workstations (just Gnome, Classical Gnome, IceWM, Classical SLE and TWM).

By the way, thanks for your help and sorry for the inconvenience.

So, you are using Gnome with Wayland configured perhaps? Does logging in with IceWM session work?

WINDOWMANAGER=/usr/bin/icewm startx

if you can manage a root login on any of the vttys should generate /var/log/Xorg.0.log. If you can capture it maybe we can find video= parameters to force the VGA output on.

video=VGA-1:1024x768@60:e
or
video=VGA-1:1920x1080@60:e

might be enough to get lucky. If either work, try

video=LVDS-1:d

to turn off the laptop screen.

Yes, Wayland doesn’t operate as a standalone server like Xorg, so no logging as such. Instead it’s the Wayland compositor (Mutter in the case of Gnome?) and the application(s) involved that need to be examined when graphical issues are encountered…

Given the age of the laptop, maybe it would help to prevent GDM from starting until this gets sorted out. Append a 3 to the kernel cmdline at the Grub menu.

The cold hp8710w screen waked up a couple of hours again today with its stripes, shadows and grain, but yet readable :expressionless:

I’m fairly sure I did a standard Leap 15 with Gnome desktop installation as on my other Dell XPS13 ultrabook and Asus workstation last time. Yet, the hp8710w’s GDM session menu lacks the “Gnome on Xorg” option which is available on my two other machines.
HP has only two of three Gnome options; “Gnome” (which is with Wayland), Classic Gnome (and the SLE standard custom variant).
I don’t know if the grahics issue has influenced why Gnome on Xorg lacks on the the hp8710 GDM session menu.

While the hp8710w local display was “readable working”, I noticed a difference that 1920x1200 resolution was back and saved this output:

linux-iv5y:~ # xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
default connected primary 1920x1200+0+0 0mm x 0mm
   1920x1200     77.00* 

linux-iv5y:~ # xrandr --prop
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
default connected primary 1920x1200+0+0 0mm x 0mm
    _MUTTER_PRESENTATION_OUTPUT: 0 
   1920x1200     77.00* 

inxi -Gxx
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
Graphics:  Card: NVIDIA G92GLM [Quadro FX 3600M] bus-ID: 01:00.0 chip-ID: 10de:061c
           Display Server: X.org 1.19.6 driver: N/A tty size: 111x28 Advanced Data: N/A for root

Later at next startup, the screen was unreadable again, but I’m able to enter the Gnome session login yet (blindfolded) so that the wifi startup, and with its ip-address already preserved it connected fine from another workstation using “ssh -X” and “sftp gui fro copying in Nautilus”.

Started and stopped X within the ssh root connection;


linux-iv5y:~ # WINDOWMANAGER=/usr/bin/icewm startx
hostname: Name or service not known
xauth:  file /root/.serverauth.4269 does not exist


X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux linux-iv5y 4.12.14-lp150.12.16-default #1 SMP Tue Aug 14 17:51:27 UTC 2018 (28574e6) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp150.12.16-default root=UUID=3fc2e6a3-5c9c-4747-9f39-c1d8b9a0b8e4 nouveau.modeset=0 resume=/dev/disk/by-label/swap splash=silent quiet showopts
Build Date: 17 April 2018  12:00:00PM
 
Current version of pixman: 0.34.0
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue Sep 18 16:38:31 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Failed to connect to bus: No such file or directory
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale nb_NO.UTF-8 ...
Checking for a default input method in /etc/X11/xim.d/nb/
sourcing /etc/X11/xim.d/nb/40-ibus ...
/etc/X11/xim.d/nb/40-ibus started sucessfully
^Cxinit: connection to X server lost

waiting for X server to shut down XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
      after 58521 requests (58521 known processed) with 1 events remaining.
(II) Server terminated successfully (0). Closing log file.

xinit: unexpected signal 2
-------------------------------------------------------------------------------------------
xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local and run "chkstat --system --set" afterwards

Now a fresh /var/log/Xorg.1.log was found (not Xorg.0.log), but hopefully it contains the wanted info(?). But the content is 6918 words, which is too large for this post. What information should I possibly capture?

From ssh I tried the mentioned

video=VGA-1:1920x1080@60:e

and rebooted hp8710w. This caused the laptop boot sreen became readable again with the chaned resolution, but no VGA input to the external monitor.

video=LVDS-1:d

and rebooted. This had no effect on the hp8710w display nor on the VGA connected monitor.

77 refresh on a LCD is something I’ve never seen before. Maybe it should be tried to force 60 via appending to kernel cmdline:

video=@60
linux-iv5y:~ # xrandr --prop
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
default connected primary 1920x1200+0+0 0mm x 0mm
    _MUTTER_PRESENTATION_OUTPUT: 0 
   1920x1200     77.00* 

inxi -Gxx
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
Graphics:  Card: NVIDIA G92GLM [Quadro FX 3600M] bus-ID: 01:00.0 chip-ID: 10de:061c
           Display Server: X.org 1.19.6 driver: N/A tty size: 111x28 Advanced Data: N/A for root

I’ve never seen inxi fail to report any X driver before, but maybe this is another Wayland difference?

Later at next startup, the screen was unreadable again, but I’m able to enter the Gnome session login yet (blindfolded) so that the wifi startup, and with its ip-address already preserved it connected fine from another workstation using “ssh -X” and “sftp gui fro copying in Nautilus”.

Started and stopped X within the ssh root connection;


linux-iv5y:~ # WINDOWMANAGER=/usr/bin/icewm startx
hostname: Name or service not known
xauth:  file /root/.serverauth.4269 does not exist


X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux linux-iv5y 4.12.14-lp150.12.16-default #1 SMP Tue Aug 14 17:51:27 UTC 2018 (28574e6) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp150.12.16-default root=UUID=3fc2e6a3-5c9c-4747-9f39-c1d8b9a0b8e4 nouveau.modeset=0 resume=/dev/disk/by-label/swap splash=silent quiet showopts
Build Date: 17 April 2018  12:00:00PM
 
Current version of pixman: 0.34.0
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue Sep 18 16:38:31 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Failed to connect to bus: No such file or directory
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale nb_NO.UTF-8 ...
Checking for a default input method in /etc/X11/xim.d/nb/
sourcing /etc/X11/xim.d/nb/40-ibus ...
/etc/X11/xim.d/nb/40-ibus started sucessfully
^Cxinit: connection to X server lost

waiting for X server to shut down XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
      after 58521 requests (58521 known processed) with 1 events remaining.
(II) Server terminated successfully (0). Closing log file.

xinit: unexpected signal 2
-------------------------------------------------------------------------------------------
xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local and run "chkstat --system --set" afterwards

Maybe Xorg is not setuid. You can try again after setting it thus:

chmod 4711 /usr/bin/Xorg

It seems also IceWm was not installed, so install it

zypper in icewm

and try again.

Now a fresh /var/log/Xorg.1.log was found (not Xorg.0.log), but hopefully it contains the wanted info(?). But the content is 6918 words, which is too large for this post. What information should I possibly capture?
Upload it. Try the susepaste command (install if necessary), or use http://susepaste.org and provide the URL here.

From ssh I tried the mentioned

video=VGA-1:1920x1080@60:e

and rebooted hp8710w. This caused the laptop boot sreen became readable again with the chaned resolution, but no VGA input to the external monitor.

video=LVDS-1:d


and rebooted. This had no effect on the hp8710w display nor on the VGA connected monitor.

I don’t know how these video= kernel cmdline options are supposed to do anything after booting. These need to be appended to the kernel line at the Grub menu by using the e key when the Grub menu appears.

IceWm was already installed. Did chmod 4711 and tried again via remote ssh -X.

WINDOWMANAGER=/usr/bin/icewm startx

The IceWm desktop was not redirected, so I had to stop it after a while as previous with Ctrl-C (could possibly run it in background). The only output difference was that the text below the stippled line did not appear more.

Upload it. Try the susepaste command (install if necessary), or use http://susepaste.org and provide the URL here.

The lastest /var/log/Xorg.1.log is here SUSE Paste

I don’t know how these video= kernel cmdline options are supposed to do anything after booting. These need to be appended to the kernel line at the Grub menu by using the e key when the Grub menu appear
s.

The problem is that the 8710w screen isn’t readable on most attempts, not even during startup. Tried instead via remote ‘ssh -X’ the ‘yast2 bootloader’ and added the kernel parameter ‘video=VGA-1:1920x1080@60:e’
Saved yast and rebooted. But still no Video input on the VGA connected monitor. (tested this monitor and VGA cable previous today connected to the XPS-13 ultrabook, and the video signal appeared automatic as dual monitor at first attempt without any setup.)

Error 404. :frowning:

Sorry, I tested it but maybe it expired. New attempt:

http://susepaste.org/22635853
http://paste.opensuse.org/22635853

The log reports nouveau.modeset=0 on the kernel cmdline, which prevents all competent X drivers except NVidia from being used. The NVidia driver is also not being used (I don’t know why - I never use any proprietary driver). Thus, X is falling back to the FBDEV driver, which is basically an emergency-only fallback driver incapable of running GDM and Gnome. Either the NVidia driver and its requirements need to be completely eradicated and nouveau.modeset=0 removed from the kernel cmdline so that the nouveau X driver or the modesetting X driver can be used to achieve 1920x1200, or an appropriate proprietary NVidia driver for your Quadro FX 3600M, if one exists to match the 15.0 kernel, must be correctly installed, if you wish GDM and Gnome to work.

Because using the FBDEV driver results in no report of CRTC names, I still don’t know what names would be required for video= on kernel cmdline to possibly be effective. AFAIK, FBDEV is incapable of producing output on more than one display, so first order of business must be to get X using a competent driver, either NVIDIA (keeping nouveau.modeset=0 on cmdline), or modesetting or nouveau (with nouveau.modeset=0 removed from cmdline).

Bad news;
I lost the last viewable access point (remote ssh) I had to 8710w after removing ‘nouveau.modeset=0’ from the kernel parameters with ‘yast2 bootloader’ (kept the ‘video=VGA-1:1920x1080@60:e’). Then rebooted and on startup there was a short ray of hope, as both the external vga connected monitor and the laptop panel displayed video graphics (yet distorted), but then froze with the green Leap router logo image. After that 8710w freezes on each startup attempt, and I cannot longer logon blindfolded to get wifi network for access with remote ssh.

I think ‘nouveau.modeset=0’ was suggested long time ago to get Leap installed without freeze on hp8710w, which has worked with useable graphics at its wuxga resolution 1920x1200 several years, Leap15 included up the graphics failure occured in recent time. Because I didn’t install the Nvidia prepared kernel for openSUSE, I have thought it was still the standard nouveau driver that was used.

Before the ssh disconnected I also ran the following two commands to verify the graphics and session type in use:

inxi -Fxz
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
System:    Host: linux-iv5y Kernel: 4.12.14-lp150.12.16-default x86_64
           bits: 64 gcc: 7.3.1
           Desktop: N/A Distro: openSUSE Leap 15.0
Machine:   Device: laptop System: Hewlett-Packard product: HP Compaq 8710w v: F.0F serial: N/A
           Mobo: Hewlett-Packard model: 30C3 v: KBC Version 73.31 serial: N/A
           BIOS: Hewlett-Packard v: 68MAD Ver. F.0F date: 11/25/2008
Battery    C1FD: charge: 0.0 Wh 0.0% condition: 37.7/37.7 Wh (100%)
           model: Hewlett-Packard Primary status: Charging
CPU:       Dual core Intel Core2 Duo T9500 (-MCP-) 
           arch: Penryn rev.6 cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 10373
           clock speeds: max: 2601 MHz 1: 1200 MHz 2: 800 MHz
Graphics:  Card: NVIDIA G92GLM [Quadro FX 3600M] bus-ID: 01:00.0
           Display Server: X.org 1.19.6 driver: N/A tty size: 80x24
.................
loginctl show-session $(loginctl | grep $(whoami) | awk '{print $1}') -p Type
Type=tty

Type=x11

Expired again already. You need not accept the short expiration when submitting.

I wanted to see what was on the kernel cmdline, which Xorg.#.log provides. Just guessing it still includes quiet and/or splash=silent. If present, remove both. If neither/both help, add plymouth.enable=0. Try with and without nomodeset, depending on which X driver you are hoping will work, but you shouldn’t need both. Plymouth and NVidia commonly do not play nice together.

This error will go away if you install Mesa-demo-x.

Graphics:  Card: NVIDIA G92GLM [Quadro FX 3600M] bus-ID: 01:00.0
           Display Server: X.org 1.19.6 driver: N/A tty size: 80x24
.................

This confirms no X driver has succeeded to load.