Xorg causes all ttys to become black/corrupted

Drone91 · 03-25-2007, 03:04 PM

The problem is this -
I installed OpenBSD 4.0 on my machine
all runs fine except when i start xorg, all the tty's show (rubbish when change ciinsole while x runs and when i shut x down they are black
the cursor shows in the second case and they react normally in both
my graphic card is Nvidia GEforce 5200 i am using the nv driver
also what i have noticed while trying the configurations is that the vesa driver does not work at all (probably unrelated and not a problem, but might help)
on Internet i did not found anything helpful except one had similar problem on netbsd byt the post was from 2002, but i found not much of use there.
Hope somebody will be able to help

GrapefruiTgirl · 03-26-2007, 09:42 PM

First off, I must say I LOVE your signature! That is extremely funny about 'Window$ -n.'

Now... I don't use *BSD and know next to nothing about it, but I do use an nVidia GeForce card. It would be very helpful if you would post your xorg.conf file.
The VESA driver doesn't work very well, you're right. But by the sounds of things, it sounds like your frame-buffer device is misconfigured or video memory is getting corrupted/overwritten. I had a VERY similar effect as you describe when I was using a wrong depth and resolution to the console framebuffer. When I exited Xorg, all the text that was supposed to be on the screen was exploded all over the screen in different colors, and totally unreadable, and I couldn't see what I was typing.

One thing I definitely recommend is that you download and install the BSD nVidia driver from www.nvidia.com for your card. Also, what is the onboard video device on your computer?
After that, post your xorg.conf, as well as the output from the command 'lspci' (I presume BSD uses the same commands/syntax as Linux; please correct me if I'm wrong)

Drone91 · 03-27-2007, 02:36 PM

#1 am using 80x25 console, since there is no framebuffer on OBSD
#2a similar program (pcitweak) returned this

Code:

PCI: PCI scan (all values are in hex)
PCI: 00:00:0: chip 10de,01e0 card 0000,0000 rev c1 class 06,00,00 hdr 80
PCI: 00:00:1: chip 10de,01eb card 1462,5700 rev c1 class 05,00,00 hdr 80
PCI: 00:00:2: chip 10de,01ee card 1462,5700 rev c1 class 05,00,00 hdr 80
PCI: 00:00:3: chip 10de,01ed card 1462,5700 rev c1 class 05,00,00 hdr 80
PCI: 00:00:4: chip 10de,01ec card 1462,5700 rev c1 class 05,00,00 hdr 80
PCI: 00:00:5: chip 10de,01ef card 1462,5700 rev c1 class 05,00,00 hdr 80
PCI: 00:01:0: chip 10de,0080 card 1462,5700 rev a3 class 06,01,00 hdr 80
PCI: 00:01:1: chip 10de,0084 card 1462,5700 rev a1 class 0c,05,00 hdr 80
PCI: 00:02:0: chip 10de,0087 card 1462,5700 rev a1 class 0c,03,10 hdr 80
PCI: 00:02:1: chip 10de,0087 card 1462,5700 rev a1 class 0c,03,10 hdr 80
PCI: 00:02:2: chip 10de,0088 card 1462,5700 rev a2 class 0c,03,20 hdr 80
PCI: 00:04:0: chip 10de,008c card 1462,570c rev a3 class 06,80,00 hdr 00
PCI: 00:06:0: chip 10de,008a card 1462,0080 rev a1 class 04,01,00 hdr 00
PCI: 00:08:0: chip 10de,008b card 0000,0000 rev a3 class 06,04,00 hdr 01
PCI: 00:09:0: chip 10de,0085 card 1462,5700 rev a3 class 01,01,8a hdr 00
PCI: 00:0b:0: chip 10de,008e card 1462,5700 rev a3 class 01,01,85 hdr 00
PCI: 00:1e:0: chip 10de,01e8 card 0000,0000 rev c1 class 06,04,00 hdr 01
PCI: 02:00:0: chip 10de,0322 card 0000,0000 rev a1 class 03,00,00 hdr 00
PCI: End of PCI scan

#3 xorg.conf

Code:

Section "Module"
    Load        "dbe"   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
#    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath     "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/TTF/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/X11R6/lib/X11/fonts/freefont/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection
Section "InputDevice"

    Identifier  "Keyboard1"
    Driver      "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option     "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"   "xorg"
    Option "XkbModel"   "pc104"
    Option "XkbLayout"  "us"

EndSection
Section "InputDevice"

# Identifier and driver

    Identifier  "Mouse1"
    Driver      "mouse"
    Option "Protocol"    "wsmouse"      # wsmouse protocol
    Option "Device"      "/dev/wsmouse"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"  "Xqueue"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"        "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"  "9600"
#    Option "SampleRate"        "150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

# ZaxisMapping is an option for handling the wheel
#    Option "ZAxisMapping" "4 5"

EndSection
Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 79.0

#    HorizSync  30-64         # multisync
#    HorizSync  31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync  15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-100

EndSection


Section "Device"
    Identifier  "Standard VGA"
    VendorName  "Unknown"
    BoardName   "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam   256

#    Clocks     25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "** NVIDIA (generic)                   [nv]"
    Driver      "nv"
    #VideoRam    131072
    # Insert Clocks lines here if appropriate
EndSection
Section "Screen"
    Identifier  "Screen 1"
    Device      "** NVIDIA (generic)                   [nv]"
    Monitor     "My Monitor"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection
Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

GrapefruiTgirl · 03-27-2007, 08:11 PM

OK, that 'lspci' function gives less than desireable results. I don't specifically see the nVidia card in there, but it's extremely likely that it is the device at PCI:2:0:0. so in the device section for the nvidia card, add the line BusID "PCI:2:0:0"

There is probably no need to use your onboard device, but if you choose to load a driver for it, then you ought to figure out which of the remaining PCI locations refers to the onboard device location.
If you have a command similar to 'lshw' that may tell you; but it is NOT PCI:0:10:0 is it says in the commented out BusID line.
Or, try just commenting out the lines for the 'default vga' device.

Try that

but remember, I haven't yet used *BSD at all, so if I am mistaken somewhere, like for example about needing to use the onboard device for something or not, please do correct me.
Best wishes.

Drone91 · 03-28-2007, 11:57 AM

Quote:

Originally Posted by GrapefruiTgirl

OK, that 'lspci' function gives less than desireable results. I don't specifically see the nVidia card in there, but it's extremely likely that it is the device at PCI:2:0:0. so in the device section for the nvidia card, add the line BusID "PCI:2:0:0"

There is probably no need to use your onboard device, but if you choose to load a driver for it, then you ought to figure out which of the remaining PCI locations refers to the onboard device location.
If you have a command similar to 'lshw' that may tell you; but it is NOT PCI:0:10:0 is it says in the commented out BusID line.
Or, try just commenting out the lines for the 'default vga' device.

Try that

but remember, I haven't yet used *BSD at all, so if I am mistaken somewhere, like for example about needing to use the onboard device for something or not, please do correct me.
Best wishes.

You are - AFAIK (so far the manual tells, there is no onboard device on this one) i got no onboard video card.

GrapefruiTgirl · 03-28-2007, 12:09 PM

OK.... So what have you tried so far? Have you added the BusID line for PCI:2:0:0 ?
And perhaps removed the line with the vga driver?
Any other changes you have tried?

Drone91 · 03-28-2007, 01:49 PM

I tried the BusID but did not make any change
I am new with this also - i try it for to see which system will be better for future as i plan to buy an used sun blade 1000/2000 from ebay and slackware which i used before (and like best) has no sparc port
it is no hurrying matter (1/2 year at best)- the (re)install was forced because slackpkg made a disaster with update - too work extensive to fix it was

looks like i will see something else - other thing i have time as this is not of the errors that are too bad