Page 1 of 5 123 ... LastLast
Results 1 to 10 of 48

Thread: Using old laptop with dumb frame buffer and external display

  1. #1

    Default 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

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Using old laptop with dumb frame buffer and external display

    Quote Originally Posted by terjejh View Post
    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.
    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:
    Code:
    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.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

  3. #3

    Default Re: Using old laptop with dumb frame buffer and external display

    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*

  4. #4

    Default Re: Using old laptop with dumb frame buffer and external display

    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 ??

  5. #5
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Using old laptop with dumb frame buffer and external display

    Quote Originally Posted by terjejh View Post
    I searhed for Xorg.0.log, but cannot find any on the installation.
    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
    Code:
    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.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

  6. #6
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Using old laptop with dumb frame buffer and external display

    Quote Originally Posted by terjejh View Post
    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 ??
    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.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

  7. #7

    Default Re: Using old laptop with dumb frame buffer and external display

    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.

  8. #8
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    18,951
    Blog Entries
    1

    Default Re: Using old laptop with dumb frame buffer and external display

    Quote Originally Posted by terjejh View Post
    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).
    So, you are using Gnome with Wayland configured perhaps? Does logging in with IceWM session work?
    openSUSE Leap 15.0; KDE Plasma 5

  9. #9
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    700

    Default Re: Using old laptop with dumb frame buffer and external display

    Quote Originally Posted by terjejh View Post
    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).
    Code:
    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.
    Code:
    video=VGA-1:1024x768@60:e
    or
    video=VGA-1:1920x1080@60:e
    might be enough to get lucky. If either work, try
    Code:
    video=LVDS-1:d
    to turn off the laptop screen.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2) & 42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,others on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,GT218 &&&&

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    18,951
    Blog Entries
    1

    Default Re: Using old laptop with dumb frame buffer and external display

    Quote Originally Posted by mrmazda View Post
    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
    Code:
    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.
    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...

    https://fedoraproject.org/wiki/How_t...yland_problems
    openSUSE Leap 15.0; KDE Plasma 5

Page 1 of 5 123 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •