seeking help: issues with onboard nVidia — startx reports 'no screens'

Forum Forums New users New Users and General Questions seeking help: issues with onboard nVidia — startx reports 'no screens'

  • This topic has 3 replies, 3 voices, and was last updated Nov 15-3:33 pm by mmmmna.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #2171
    Member
    Avatarmmmmna

    IIRC, Antix 17 x64 chose the wrong video system in my PC. My onboard nVidia video is NOT being used, yet that install evidently configured the onboard nVidia for X, and yet my only monitor is connected to the added PCI card using ATI Radeon RV710. That system only booted to a console, startx errors said something about no screens.

    Footnote: my mainboard is completely a nVidia chipset:

    $ inxi -b
    System:    Host: 64bitantix162 Kernel: 4.4.10-antix.1-amd64-smp x86_64
               bits: 64
               Desktop: MATE 1.16.2
               Distro: antiX-16.2_x64-full Berta Cáceres 15 June 2017
    Machine:   Device: desktop Mobo: Gateway model: MCP61SM2MA v: FAB1.0 serial: N/A
               BIOS: Phoenix v: 6.00 PG date: 11/10/2007
    CPU:       Dual core AMD Athlon 64 X2 4200+ (-MCP-) speed/max: 1000/2200 MHz
    Graphics:  Card-1: NVIDIA C61 [GeForce 6100 nForce 405]
               Card-2: Advanced Micro Devices [AMD/ATI] RV710 [Radeon HD 4350/4550]
               Display Server: X.Org 1.19.2
               drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
               Resolution: 1680x1050@59.95hz
               OpenGL: renderer: Gallium 0.4 on AMD RV710 (DRM 2.43.0 / 4.4.10-antix.1-amd64-smp, LLVM 3.9.1)
               version: 3.3 Mesa 13.0.6
    Network:   Card-1: NVIDIA MCP61 Ethernet driver: forcedeth
               Card-2: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
               driver: b43-pci-bridge
    Drives:    HDD Total Size: 600.1GB (16.3% used)
    Info:      Processes: 184 Uptime: 10:21 Memory: 624.1/1877.6MB
               Client: Shell (bash) inxi: 2.3.40 
    mmmmna@64bitantix162:~
    
    • This topic was modified 2 years ago by skidoo.
    • This topic was modified 2 years ago by skidoo. Reason: split from "Sandbbox ... Synaptic" topic + retitled
    #2582
    Member
    Avatarskidoo

    (asking 4 days later, after having split this from the “Sandbox… Synaptic” topic)

    mmmmna, have you found a solution?

    #2600
    Forum Admin
    anticapitalistaanticapitalista

    Have you installed the nvidia divers?

    Philosophers have interpreted the world in many ways; the point is to change it.

    #2618
    Member
    Avatarmmmmna

    Thanks for splitting this, I’m sure I’ll need this thread in the future since my hardware won’t soon be changing!

    I’m presently running Antix 64 bit 16.2, and have only the one partition, there is no such problem in this configuration (16.2 correctly configured X graphics).

    At this point, I’m presuming I’ll end up installing 17 in a few weeks, and if this repeats, I’ll pick up the research at that time.

    But not for nothing, one point that seemed odd to me back then was how the installation process created the X configuration. When I’ve attached a monitor to one graphics card (the ATI card), why does the installation configure X for the opposite graphics system? Seems to me that a simple test (DDC monitor data) would inform the installation process that there is no monitor on the nVidia graphics port, and thus configuring X to use only that unused nVidia port is rather silly.

    Until I reinstall 64 bit Antix 17, folks have this as food for thought.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.